fix(workflows): allow github-actions[bot] to trigger recompile-safe-output-fixtures#958
Merged
Merged
Conversation
…utput-fixtures The release event is dispatched by github-actions[bot] when release-please publishes a new ado-aw release. The pre_activation gate required admin/maintainer/write roles, so the bot actor was denied and the workflow never activated for release-driven recompiles (e.g. run 27278581112). Add 'github-actions[bot]' to on.bots so the release-triggered path can activate, and recompile the lock file accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
The
elease: published event for
recompile-safe-output-fixturesis dispatched bygithub-actions[bot]when release-please cuts a newado-awrelease. The workflow's pre_activation gate enforces the default required roles (admin,maintainer,write), so the bot actor was rejected and the workflow never activated on release — e.g. run 27278581112 skipped activation with:Change
bots: ["github-actions[bot]"]toon:inrecompile-safe-output-fixtures.mdso release-triggered runs can activate.recompile-safe-output-fixtures.lock.yml(rendersGH_AW_ALLOWED_BOTS: "github-actions[bot]"env on the pre_activation step plus a bots comment underon:).Human
workflow_dispatchruns continue to go through the normal role check unchanged.