ci(electron-ota): publish with GH_ACTION_TOKEN - #2139
Open
neerajhariyale wants to merge 1 commit into
Open
Conversation
…on electron-build-repo)
Contributor
Up to standards ✅🟢 Issues
|
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
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.
Follow-up to #2137. The OTA publish workflow referenced a secret
ELECTRON_PUBLISH_TOKENthat doesn't exist, and the repo account only has pull access toelectron-build-repo— so a personal PAT can't publish there. Switch the publish step to the existingGH_ACTION_TOKENsecret (cross-repo PAT).If
GH_ACTION_TOKENlackscontents:writeonelectron-build-repo, the publish step will fail with an auth error and we'll need an org-admin token.🤖 Generated with Claude Code