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.
fix: restore interaction permissions for workflow_call workflows with reaction/status-comment #39652
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
fix: restore interaction permissions for workflow_call workflows with reaction/status-comment #39652
Changes from all commits
c37e73e363923fa1e2ecfa0710b1eaad061ab39b5a397b3f6File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
[/tdd] These three scenarios cover the GITHUB_TOKEN path well, but there is no test for the GitHub App path (
buildActivationAppTokenPermissions) — aworkflow_call+ reaction/status-comment workflow that also configuresactivation.github-appwould silently produce an app token with no write scopes.💡 Suggested test scenario
Add a fourth test with
activation.github-appconfigured to verify that the minted app-token permissions section also includesissues: write,pull-requests: write, anddiscussions: write. The existing tests only exercise the GITHUB_TOKENpermissions:block in the activation job, not thegh-app-token-permissions:block.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.
[/diagnose] The app-token path (
buildActivationAppTokenPermissions) has the same gap this PR is fixing for the GITHUB_TOKEN path — it still callsaddActivationInteractionPermissionswith the rawonSection, which will silently drop write scopes for aworkflow_call-only trigger.💡 Root-cause detail
buildActivationAppTokenPermissions(line 236) calls:addActivationInteractionPermissionsMapparses the event set and finds onlyworkflow_call— none of thehasIssuesEvent/hasPullRequestEvent/hasDiscussionEventflags fire, so no write permission is granted to the minted app token.The fix should mirror what this new function does: detect
hasWorkflowCallTriggerinbuildActivationAppTokenPermissionsand calladdBroadActivationInteractionPermissionsthere too (or extract a shared helper both paths call).Uh oh!
There was an error while loading. Please reload this page.