docs: step-by-step manual for creating WINGET_TOKEN - #710
Draft
Matovidlo wants to merge 1 commit into
Draft
Conversation
Documents how to create the org-bot classic PAT (public_repo scope) the winget release job needs, and notes the still-open bootstrap prerequisite (first wingetcreate submit) that keeps that job disabled.
There was a problem hiding this comment.
Pull request overview
Adds operational documentation to the release/distribution ADR, specifically detailing how to create and store the WINGET_TOKEN secret needed by the (currently disabled) WinGet release job.
Changes:
- Added a step-by-step guide for creating a classic PAT for
wingetcreateand storing it as arelease-scoped repo secret. - Documented constraints around using an org-owned bot account and the minimal required PAT scope (
public_repo). - Reiterated the existing blocker that keeps the WinGet job disabled until a one-time
wingetcreate submitbootstrap is performed manually.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+113
to
+116
| 1. Get (or create) an org-owned GitHub bot account for this purpose — not a personal | ||
| account. It only needs to be a regular GitHub user; it does **not** need to be a | ||
| member of the `keboola` org or have any repo permissions here, since the token is | ||
| only ever used against the external `microsoft/winget-pkgs` repo. |
Comment on lines
+126
to
+130
| 9. Store it as the repo secret, scoped to the `release` environment, piping the value | ||
| via stdin so it never lands in shell history: | ||
| ``` | ||
| gh secret set WINGET_TOKEN --env release --repo keboola/cli | ||
| ``` |
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.
Summary
docs/adr/0003-release-distribution-cicd.mdfor creating theWINGET_TOKENsecret used by the (currently disabled)wingetrelease job.public_repoonly), and setting it as arelease-scoped repo secret viagh secret set.if: false) until someone does the one-timewingetcreate submitbootstrap againstmicrosoft/winget-pkgsby hand — this PR only documents token creation, it does not perform that submission or re-enable the job.Test plan
winget:job comments in.github/workflows/release-kbagent.ymland the secrets table already in this ADR.Related
No Linear issue — follow-up from a question about what
WINGET_TOKENis used for and how to create it.