Repository navigation
Publish a GitHub prerelease for each main merge - #19
Merged
Merged
Conversation
Deploying patchling with
|
| Latest commit: |
0f216d0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://042959c6.patchling.pages.dev |
| Branch Preview URL: | https://ci-main-merge-prerelease.patchling.pages.dev |
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.
Publish a source prerelease from the exact commit produced by each pull request merged into
main. Each prerelease links back to the pull request and publishing run. Its commit-based tag makes reruns safe and keeps stable versions in the Latest slot.The release job reads GitHub merge metadata without checking out or executing the proposed code. It publishes to this repository with GitHub's repository-scoped token.
The setup merge uses GitHub's skip marker for the existing push-triggered workflows, or Cloudflare Pages' skip marker where applicable, to avoid an unrelated production deploy. The pull request checks and new release workflow still run.