-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
actions: fix PRs from forks #7549
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #7549 +/- ##
=============================================
+ Coverage 29.38% 87.49% +58.10%
=============================================
Files 1200 31 -1169
Lines 147488 1535 -145953
Branches 2894 0 -2894
=============================================
- Hits 43343 1343 -42000
+ Misses 102441 192 -102249
+ Partials 1704 0 -1704
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
In OpenRailAssociation#7549 we tried to fix CI for external contributors by using the fork repo registry instead of the base repo registry. Unfortunately GITHUB_TOKEN cannot be used to write to the fork repo registry, it only has read access to the base repo registry. Instead, use artifacts to pass around built Docker images. Co-authored-by: Simon Ser <contact@emersion.fr>
In #7549 we tried to fix CI for external contributors by using the fork repo registry instead of the base repo registry. Unfortunately GITHUB_TOKEN cannot be used to write to the fork repo registry, it only has read access to the base repo registry. Instead, use artifacts to pass around built Docker images. Co-authored-by: Simon Ser <contact@emersion.fr>
In #7549 we tried to fix CI for external contributors by using the fork repo registry instead of the base repo registry. Unfortunately GITHUB_TOKEN cannot be used to write to the fork repo registry, it only has read access to the base repo registry. Instead, use artifacts to pass around built Docker images. Co-authored-by: Simon Ser <contact@emersion.fr>
This PR is best reviewed commit by commit