fix: fixing use of PRIVATE_SUBMODULE_ACCESS_TOKEN instead of RELEASE_PAT#12
Merged
geekbrother merged 1 commit intomainfrom Oct 1, 2024
Merged
fix: fixing use of PRIVATE_SUBMODULE_ACCESS_TOKEN instead of RELEASE_PAT#12geekbrother merged 1 commit intomainfrom
PRIVATE_SUBMODULE_ACCESS_TOKEN instead of RELEASE_PAT#12geekbrother merged 1 commit intomainfrom
Conversation
chris13524
approved these changes
Oct 1, 2024
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.
This PR extends the use of the
PRIVATE_SUBMODULE_ACCESS_TOKENsecret or fallback to the github.token for all cases where the repository checkout is used.This secret should be used for the repository checkout instead of the
RELEASE_PAT. This will fix the case whenPRIVATE_SUBMODULE_ACCESS_TOKENandRELEASE_PATwere created for different orgs.