ci: automate release milestones and notify included pull requests - #3357
Merged
afonsojramos merged 2 commits intoOct 4, 2026
Merged
Conversation
Port the Atlassify release automation to Gitify: - Derive the open `Release X.Y.Z` milestone from the release-please release-PR title and keep it in step as the calculated version changes. - Finalize the milestone (release URL, due date, closed) once the release is published, on both automated and manual publish paths. - Comment once per included pull request with a link to the published release, using a hidden per-tag marker for idempotent re-runs. See openspec/changes/release-milestone-automation.
`milestone.yml` runs on `pull_request: closed` and can reach its attach step before release-please has opened the next release PR and the `milestones` job has created the new milestone. When it wins that race it finds no open milestone and skips, so the first pull request of the cycle is never attached and never notified. In the `milestones` job, after the milestone is ensured, resolve the merged pull request(s) for the push tip and attach any that do not already carry it. Idempotent (skips matching milestones), merged-only, and env-indirected. See openspec/changes/harden-release-milestone-attachment.
|
afonsojramos
approved these changes
Oct 4, 2026
afonsojramos
deleted the
ci/milestone-automation-and-pr-comment-on-release
branch
October 4, 2026 00:03
Contributor
|
🎉 This pull request is included in Gitify v7.9.0! 🎉 Downloads for macOS, Windows, and Linux are available on the release page. Thanks for helping make Gitify better! |
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
2 participants
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.
Port the Atlassify release automation to Gitify:
Release X.Y.Zmilestone from the release-please release-PR title and keep it in step as the calculated version changes.