Closed danielloader closed 9 months ago
Are you trying to skip a release-please PR completely? If so, that's not what the skip-github-pull-request
input is for. That input is so that you can separate the steps of tagging releases for a merged release-please PR from the creation of the release-please
PR.
In my test repo, I separated the steps (https://github.com/chingor13/release-please-playground/blob/62a780d6a2de961f7b9633f14982391049aa3b4b/.github/workflows/rp.yml) and it correctly tagged the release (https://github.com/chingor13/release-please-playground/pull/50#issuecomment-1852471602) when I merged the PR.
TL;DR
skip-github-pull-request: true
.It's entirely possible this is desired behaviour, but the action isn't creating a release either despite the explicit
skip-github-release: false
.If there's no scope for this project to skip the pull requests but also keep making releases/pushing tags please close this issue.
Expected behavior
Expected the action to:
Additionally, but optionally, creating the github release at the same time if desired.
Observed behavior
The action is triggered successfully on PR being merged but no mutation of the repository is observed.
Action YAML
Log output
Additional information
Previous builds have been success with
skip-github-pull-request: false
flag being left as default, to explain why there's values up to v0.0.9.I am using a PAT to avoid the github limitation of not triggering subsequent jobs using the default
GITHUB_TOKEN
to write back to the repository.The PAT has full repository read/write, and package write scopes.
This is an attempt to remove the release PR part of the workflow but retain the other part of the functionality, namely creating tags automatically on commit message prefixes being pushed to main.