Skip to content

ci: add use-main-as-release option to deploy workflow#291

Merged
mcanouil merged 1 commit intomainfrom
ci/deploy-use-main-as-release
Feb 26, 2026
Merged

ci: add use-main-as-release option to deploy workflow#291
mcanouil merged 1 commit intomainfrom
ci/deploy-use-main-as-release

Conversation

@mcanouil
Copy link
Copy Markdown
Owner

Summary

  • Add a use-main-as-release boolean input to the workflow_dispatch trigger in the deploy workflow.
  • When set to true, the "Get latest tag" and "Checkout latest tag" steps are skipped, so the release site renders from main.
  • Default behaviour (false) is unchanged: the release site renders from the latest git tag.

Test plan

  • Run the workflow manually with use-main-as-release: false and confirm it renders from the latest tag.
  • Run the workflow manually with use-main-as-release: true and confirm it renders from main.

Add a workflow_dispatch boolean input that skips the tag checkout steps,
rendering the release site from main instead of the latest git tag.
@mcanouil mcanouil added the Type: CI/CD 🤖 Issues related to continuous integration and deployment label Feb 26, 2026
@mcanouil mcanouil self-assigned this Feb 26, 2026
@mcanouil mcanouil added the Type: CI/CD 🤖 Issues related to continuous integration and deployment label Feb 26, 2026
@mcanouil mcanouil merged commit ee9fbf6 into main Feb 26, 2026
3 checks passed
@mcanouil mcanouil deleted the ci/deploy-use-main-as-release branch February 26, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: CI/CD 🤖 Issues related to continuous integration and deployment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant