chore(ci): grant pull-requests write to issue labeler workflow#9073
Merged
Conversation
Labeling pull requests requires pull-requests: write, not just issues: write. Regression from #9058 when GH_TOKEN was replaced with scoped GITHUB_TOKEN.
Contributor
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9073 +/- ##
==========================================
+ Coverage 62.50% 63.55% +1.06%
==========================================
Files 256 319 +63
Lines 12714 21883 +9169
Branches 3023 3932 +909
==========================================
+ Hits 7945 13905 +5960
- Misses 4755 7571 +2816
- Partials 14 407 +393
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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
1 participant
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.
Description
Fixes a permissions regression from #9058 where
issue-labels.yamlwas scoped toissues: writeonly after replacingsecrets.GH_TOKENwith the defaultGITHUB_TOKEN.When a PR author replies on an open pull request, the labeler calls
issues.addLabels/issues.removeLabel. GitHub requirespull-requests: writefor PRs (403:Resource not accessible by integration;x-accepted-github-permissions: issues=write; pull_requests=write).Adds
pull-requests: writeto matchstale.ymlin the same PR.Related issues
Release Summary
N/A — CI workflow only.
Checklist
AndroidiOSOther(macOS, web)e2etests added or updated inpackages/**/e2ejesttests added or updated inpackages/**/__tests__Test Plan
Needs Attentionadded andblocked: customer-responseremovedpull-requests: writeforcreateComment)Missed label updates since #9058 merged (2026-06-20)
Audited 43 labeler runs since merge. 4 open-PR OP replies failed at the label step with 403; labels were not applied:
Expected automation for each: add
Needs Attention, removeblocked: customer-response(if present). None currently have labels.Also failed (closed PR path, not labels): #9057 — OP comment on merged PR; bot reply not posted (run).
Issue-only OP replies succeeded (e.g. #9066, #9067, #9069) —
issues: writeis sufficient for issues.Think
react-native-firebaseis great? Please consider supporting the project with any of the below:React Native FirebaseandInvertaseon Twitter