ci: backport auto-publish workflow to release-0.1#200
Merged
Roming22 merged 2 commits intoMay 11, 2026
Merged
Conversation
Replace the DOCS_RELEASE_BRANCH repository variable with automatic semver detection. The tag job now queries all release-* branches and picks the highest version, so no manual variable update is needed when cutting new releases. Follow-up to redhat-appstudio#182. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a comprehensive README.md in the docs/ directory covering: - Branch model and contributing workflow - How to get changes onto the live site (backport to release branch) - Detailed explanation of the three CI jobs (tag, build, deploy) - Local build instructions - Directory structure with file descriptions - AsciiDoc attributes reference - How to add new pages - Antora-specific notes for contributors Requested by Romain in the PR redhat-appstudio#182 discussion. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
docs/README.mdtorelease-0.1release-0.1use the old workflow and never trigger thetag→build→deploypipelinerelease-0.1will auto-tag and publish to GitHub PagesThis is why the live site at https://redhat-appstudio.github.io/tsf-cli/ has not been updating — the workflow file on
release-0.1was still the old version.Cherry-picked commits
2aceefb5— ci: auto-detect latest release branch for docs publishingdd0566ac— docs: add docs/README.md for publishing workflowTest plan
Docsworkflow runs onrelease-0.1with thetagjobdocstag is created and points to the latestrelease-0.1commit🤖 Generated with Claude Code