Use non-default token for builds to ensure cross-org repo accessibility#531
Merged
fantkolja merged 2 commits intoMay 26, 2026
Conversation
Comment out the push trigger for the main branch.
fantkolja
approved these changes
May 26, 2026
fantkolja
deleted the
Use-non-default-token-for-builds-to-ensure-cross-org-repo-accessibility
branch
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
2 participants
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 workflow introduced in #527 uses the default token, whose access is restricted to the workflow the action is executing inside of, hence when used to access other repos it errors:
Instead we should use a org-scoped PAT.
I have not tested this change as unsure of the side effects of executing workflow.