ci: auto-detect latest release branch for docs publishing#197
Merged
Roming22 merged 2 commits intoMay 6, 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>
gtrivedi88
force-pushed
the
ci/auto-detect-release-branch
branch
from
37e1841 to
dd0566a
Compare
|
@gtrivedi88: The following matrix E2E test has Failed, say /retest to rerun failed tests. Total child pipelines: 2 Failed child pipelines
|
3 tasks
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
3 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_RELEASE_BRANCHrepository variable with automatic semver detectiontagjob now queries allrelease-*branches viagit ls-remoteand picks the highest versionFollow-up to #182 per @Roming22's feedback.
How it works
When
release-0.2is cut, pushes torelease-0.1automatically stop publishing — no repo settings change needed.After merge
The
DOCS_RELEASE_BRANCHrepository variable can be removed from Settings → Secrets and variables → Actions → Variables (if it was set).Test plan
release-0.1→ tag job detects it as latest → tags and deploysrelease-0.2exists, push torelease-0.1→ tag job skips (0.2 is latest)🤖 Generated with Claude Code