-
Notifications
You must be signed in to change notification settings - Fork 12
makefile changes for monorepo prep #1097
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #1097 +/- ##
=======================================
Coverage 97.26% 97.26%
=======================================
Files 454 454
Lines 37362 37362
=======================================
Hits 36341 36341
Misses 1021 1021
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. 📢 Thoughts on this report? Let us know! |
Swatinem
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First time I hear about this setting, so I looked it up:
These config entries specify Git-tracked directories that are considered safe even if they are owned by someone other than the current user. By default, Git will refuse to even parse a Git config of a repository owned by someone else, let alone run its hooks […]
This makes total sense. But I also wonder why we need git access at all within the container?
Do you know what would happen if we just remove this, along with the apt-get install git above?
until recently (codecov/gha-workflows#42) we invoked the CLI inside the container which uses in umbrella i'd like to try using a repo-wide lockfile and sharing more docker stuff, so was gonna punt until then to figure this out |
needed for codecov/umbrella#4
we bindmount our local
workerinto the docker container. currently our localworkeris the actual git repo, so thegitinvocation works. in umbrella, it's not the actual git repo, so the command failsapparently this is all i need to change...?