Change this token name to make it more specific to its usage#31
Merged
derekmisler merged 1 commit intodocker:mainfrom Feb 9, 2026
Merged
Conversation
Contributor
Author
|
/describe |
|
✅ PR description has been generated and updated! |
krissetto
approved these changes
Feb 9, 2026
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.
Closes https://github.com/docker/gordon/issues/98
Summary
Renames the
ORG_MEMBERSHIP_TOKENsecret toCAGENT_ORG_MEMBERSHIP_TOKENto make its purpose more explicit and avoid naming conflicts with other GitHub Actions workflows that might use generic org membership tokens.Changes
Breaking Changes
Yes - Existing workflows using this action must rename their secret from
ORG_MEMBERSHIP_TOKENtoCAGENT_ORG_MEMBERSHIP_TOKEN. The workflow will fail with a clear error message if the old secret name is still in use.How to Test