Allow snapshot publication on PRs via publish-snapshot label#87
Merged
Conversation
Adds a pull_request trigger (including the labeled event) to the publish-artifacts workflow. PR-triggered runs only proceed when the publish-snapshot label is present, skip the docs/site deploy steps, and refuse to publish if the version is not a -SNAPSHOT. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011s8pDErVG9mvJwGQJWCBDk
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.
Summary
pull_requesttrigger (types:opened,synchronize,reopened,labeled) topublish-artifacts.ymlso the snapshot publication flow can run on PRs.publishjob only runs for PR events when thepublish-snapshotlabel is present; pushes tomainandv*tags behave exactly as before.sitebranch.-SNAPSHOTversion, so labeling a release version-bump PR cannot accidentally publish a release.Notes
publish-snapshotlabel to an open PR triggers a run immediately (via thelabeledevent); subsequent pushes to a labeled PR also publish.verify-docs-updated.shclassifies workflow files as non-code, so no changelog entry is required.🤖 Generated with Claude Code
https://claude.ai/code/session_011s8pDErVG9mvJwGQJWCBDk