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.
Thank you for providing such a useful tool.
When I was installing it, I found some parts of the README that needed updating, so I created a pull request.
permissions
The permissions given to the GITHUB_TOKEN for the job should be minimal.
In some articles, they choose the “Read and write permissions” button in the “Workflow permissions” section under “Settings > Actions > General”.
However, we can use
permissions
to modify the default permissions granted to the GITHUB_TOKEN.ref: https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#permissions
Additional setting
After setting
permissions
, there is one more setting required to run tagpr.For this reason, I propose adding this setting to the README.
Here is final minimum setting for running tagpr:
actions/checkout
To prevent the following warning, I propose using newer version.
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3.