Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #726 +/- ##
=======================================
Coverage 94.87% 94.87%
=======================================
Files 60 60
Lines 3278 3278
=======================================
Hits 3110 3110
Misses 168 168
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
triagejob (actions/labeler) fails on every fork PR withHttpError: Resource not accessible by integration: on thepull_requestevent GitHub capsGITHUB_TOKENat read-only for forks, whatever the job declares. Seen on #724 (run 39983016236).This moves the job to its own
triage.ymlworkflow onpull_request_target, which runs in the base repo context with a writable token. It stays safe because the job never checks out PR code: the labeler reads the changed files and.github/labeler.ymlthrough the API. Permissions are unchanged (contents: read,pull-requests: write).Note:
pull_request_targetruns the workflow file frommain, so the new job only starts running once this is merged.Checked with actionlint and zizmor (only remaining finding is the tag pin, same convention as the other workflows).