If you need to push the homebrew tap to another repository, you must create a custom Personal Access Token with repo permissions and add it as a secret in the repository. GITHUB_TOKEN permissions are limited to the repository that contains your workflow. issues: write if you use milestone closing capability.packages: write if you push Docker images to GitHub.When done, you will see your token we just created in the Personal Access Tokens box. In the next box (Create a new Personal Access Token) set the name of your Token (i used homebrew but you can use anything you want). or just contents: read if you don't need any of the above In the box with the title Personal Access Tokens, press the Create new token button. publish to Homebrew, or Scoop (assuming it's part of the same repository).The following permissions are required by GoReleaser: Your GoReleaser Pro License Key, in case you are using the goreleaser-pro distribution Working directory (below repository root)įollowing environment variables can be used as step.env keys Name The Homebrew search (the function that keeps asking me to create the token) still fires, regardless, so Im not sure how necessary the token really is, but I dont want to get blocked by the Github Police, in any case. GoReleaser distribution, either goreleaser or goreleaser-pro helper osxkeychain /usr/bin/git: line 1: syntax error near unexpected token newline /usr/bin/git: line 1: <. goreleaser.yaml signs : - artifacts : checksum cms : gpg2 args : - "-batch" - "-u" - "" Customizing ¶ Inputs ¶įollowing inputs can be used as step.with keys Name
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |