Release workflow: stable-named tarball and docs refresh issue - #422
Merged
Conversation
- Upload redmine_gtt.tar.gz alongside the versioned archive so releases/latest/download links stay valid across releases (used by the website getting-started; backfilled manually on v7.1.0) - Open a 'Docs refresh for <tag>' issue with a checklist for doc/ screenshots, guides, README and the website on every release
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
1 participant
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.
Follow-up to #421, addressing two ways release docs go stale:
redmine_gtt.tar.gzasset, so the version-independent linkhttps://github.com/gtt-project/redmine_gtt/releases/latest/download/redmine_gtt.tar.gzalways resolves to the latest release. The getting-started section on gtt-project.org switches to this link, so the website no longer needs a version bump per release. (Backfilled manually on v7.1.0; the link already works.)
Docs refresh for <tag>issue (labeldocumentation) with a checklist coveringdoc/screenshots, getting-started, api.md, README and the website. Close it directly when nothing user-visible changed. This trades silent screenshot rot for a visible reminder; actually retaking screenshots stays a human step.Adds
issues: writeto the workflow token for the issue creation.