Repository navigation
ci: publish edgetx_2.11 (LTS) from the shared workflow - #20
Merged
Merged
Conversation
edgetx_2.11 is still maintained but is GitBook content with no MkDocs config or tooling. The publish workflow can now be called via workflow_call; for GitBook-era branches it checks out the tooling from the latest release branch, converts the caller's branch with import_legacy_gitbook.py and deploys the generated config. edgetx_2.11 carries a small caller workflow, since a push there can only run workflows committed on that branch. Concurrency moves to job level so it also applies to called runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pfeerick
force-pushed
the
publish-2.11
branch
from
October 23, 2026 09:09
a68a738 to
74bf9ac
Compare
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.
Summary
edgetx_2.11is an LTS branch and still maintained, so its docs should republish on every push the waymainandedgetx_2.12do. The branch is still GitBook content, though, with no MkDocs config or tooling. And a push to it can only run workflows committed on that branch.This PR makes
publish-versioned-docs.ymlreusable:workflow_calltrigger.edgetx_2.4–edgetx_2.11), it checks out the tooling from the latest release branch, runstools/import_legacy_gitbook.py --ref origin/<branch>, and deploys the generated config withmike deploy --config-file.main/edgetx_2.12build from their ownmkdocs.ymlas before, at the pushed commit.concurrencyfrom workflow level to job level. Called runs then share the same lock, and a caller and callee can't deadlock on one group.caseentries into one pattern.#21 adds the caller workflow on
edgetx_2.11. It needs this PR merged intoedgetx_2.12first, because it referencespublish-versioned-docs.yml@edgetx_2.12.Stacking
This PR's base is
version-banners(#18), because both PRs touch the "Publish docs with mike" step. Once #18 is merged, GitHub will retarget this PR toedgetx_2.12.Testing
I extracted the version-resolution script from the workflow YAML and ran it for each branch name:
main→devedgetx_2.12→2.12 latestedgetx_2.11andedgetx_2.4→ GitBook source, tooling fromedgetx_2.12, config.site-legacy-generated/<v>/mkdocs.ymlThe import + deploy path itself is the same one I ran by hand earlier to publish 2.4–2.11.
🤖 Generated with Claude Code