Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dersimn/github-actions-semantic-release
https://github.com/dersimn/github-actions-semantic-release
Last synced: about 14 hours ago
JSON representation
- Host: GitHub
- URL: https://github.com/dersimn/github-actions-semantic-release
- Owner: dersimn
- Created: 2024-10-15T21:24:31.000Z (about 1 month ago)
- Default Branch: master
- Last Pushed: 2024-10-15T21:31:53.000Z (about 1 month ago)
- Last Synced: 2024-10-17T09:31:08.283Z (about 1 month ago)
- Size: 2.93 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Read section about GitHub authentication on [npm @semantic-release/github](https://www.npmjs.com/package/@semantic-release/github).
## tl;dr:
Using the GITHUB_TOKEN works, __but__ it won't trigger any following Workflows. You can still use this if your only goal is to provide a downloadable zip file as GitHub Release.
If you want to trigger a following Workflow, you need to issue a Personal Access Token and specify this as Secret for the Action to use. In this case the `permissions` section in YAML is still needed (for some reason - I thought the job would be able to push to the repo because the PAT has sufficient rights, but apparently there is some additional twist).
Permissions for a Personal Access Token (classic) must be at least:
![](docs/pat_classic.png)
For a _Fine-grained personal access token_ use the same permissions as in the YAML file.
## Clean Testing
For clean testing, re-create the Repository on GitHub when it gets to polluted with Tags and Releases:
gh repo delete --yes
gh repo create --public ${${$(git remote get-url origin)##*/}%.git}
gh secret set PERSONAL_ACCESS_TOKEN --body ''git tag | xargs git tag -d
git push -u origin master# Links
- https://github.com/orgs/community/discussions/55906
- https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow