Conversation
Both failing workflows failed for the same reason: `secrets.GH_PAT` is not configured on this repo, so the input resolved to an empty string and the action refused to start. PR Author Auto Assign Input required and not supplied: repo-token release-please release-please failed: Input required and not supplied: token Both now prefer `GH_PAT` and fall back to `github.token`, which is always populated. Each job already holds the permissions its action needs, so nothing depends on a secret being set. If the org sets `GH_PAT` later it takes precedence with no further change. This has to land on master to take effect. 908f19a and a88de87 both changed auto-author-assign.yml on a feature branch and neither ran: pull requests whose base branch already carried a working token still failed with the empty-input error, so `pull_request_target` is not resolving the workflow from the base. The copy on the default branch is the one that executes. For release-please the built-in token has a known cost: events created with GITHUB_TOKEN do not trigger workflows, so the release PR will not run the pull_request checks. Noted in the file.
razbroc
changed the title
|
🎫 Related Jira Issue: MAPCO-11679 |
GH_PAT turned out to be configured after all (the org secret is granted to this repo), so the long write-up about it being missing was wrong. Keep just the one line that says why the fallback is there.
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.
auto-author-assignandrelease-pleasepassedsecrets.GH_PATwith no fallback, so if that secret is ever missing the jobs fail withInput required and not supplied.Both now use
${{ secrets.GH_PAT || github.token }}.GH_PATstill wins when it is set;github.tokenis always populated and both jobs already hold the permissions those actions need.One caveat, noted in the workflow file: on the
github.tokenfallback path, the release PR that release-please opens will not run thepull_requestchecks, because events created byGITHUB_TOKENdo not trigger workflows. The release itself is unaffected.Ref MAPCO-11679.