feat(ci): add workflow_dispatch to promote-stable-docs (cherry-pick to stable) - #3081
Merged
Merged
Conversation
The auto path (workflow_run on release-superdoc.yml) only fires when SuperDoc itself releases on stable. Stable bundle runs that ship CLI/SDK/MCP without a SuperDoc release leave docs-stable behind, as does any docs-only refresh between SuperDoc versions. Add a manual trigger that pushes the current origin/stable head (or a specified SHA via the `sha` input). The auto path keeps the v* tag detection so a no-op semantic-release run still cannot advance docs; the manual path trusts the operator. No --force, so non-fast-forward attempts are rejected by GitHub.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Cherry-picks 6569085 from #3080 onto `stable` so the workflow_dispatch trigger is available when the workflow is invoked from the stable branch ref.
`workflow_dispatch` resolves the workflow file from the branch you dispatch against, so the trigger only works on stable once the file actually exists there. Without this cherry-pick, the manual promotion path is only usable from main/feature branches even after #3080 lands.
Same diff as #3080 — no logic changes.