ci: make release-please manual-only#8
Merged
Merged
Conversation
drop push trigger; workflow_dispatch only. merges to main no longer auto-cut a release PR or tag. run from Actions tab when a release is intended.
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.
Removes the
pushtrigger fromrelease-please.ymlso merges tomainno longer auto-cut a release PR or tag. The workflow remains available viaworkflow_dispatch(Actions tab) for when a release is intentionally desired.Why
The repo is being made public so org-level Actions secrets (
RELEASE_BOT_APP_ID/RELEASE_BOT_PRIVATE_KEY) resolve — on the Free plan those secrets aren't delivered to private repos, which is why the release-please job was failing. But auto-releasing on every merge is not wanted yet, so this gates release-please behind a manual dispatch.Effect
main.go-build/lint) unaffected.