create coverage data in monorepo-friendly way #1178
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
needed for https://github.com/codecov/umbrella/pull/17
currently the docker image is built and coverage data is generated as if
codecov-api
is its own repo and all the files are in the repo root. inumbrella
that is no longer true -codecov-api
exists inapps/codecov-api/
and we want that prefix to be applied to every source file we have data forthis PR sets up
codecov-api
in/app/apps/codecov-api
instead of/app
inside the docker containercodecov-api
, path fixing strips those extra directories off the path and nothing is different (see this PR's indirect changes for example)umbrella
, path fixing will strip/app
butapps/codecov-api
will remain like we want (see https://github.com/codecov/umbrella/pull/17 for example)Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.