Skip to content

ci: split build check from manual publish - #155

Open
davidfrigolet wants to merge 1 commit into
masterfrom
ci/manual-release-master
Open

ci: split build check from manual publish#155
davidfrigolet wants to merge 1 commit into
masterfrom
ci/manual-release-master

Conversation

@davidfrigolet

Copy link
Copy Markdown
Collaborator

What

Aligns docs-site CI/CD with the rest of the Flamingock projects: work directly on master, pushes never publish, publishing is a manual GitHub action.

  • build.yml (new): runs yarn build on push to master / release/** and on PRs to master. Verifies the site compiles. Never publishes.
  • deploy.yml (changed): push: master trigger removed → now workflow_dispatch only. Renamed to "Publish Flamingock Docs site". Publishing to docs.flamingock.io is a deliberate manual run; GitHub's run-workflow dropdown lets you pick the ref (master, release/1.4, release/1.5, …).
  • RELEASE.md (new): documents the model, day-to-day flow, how to publish, and how to cut release/x.y branches.

Follow-ups (not in this PR)

  • Reconcile master with develop (separate PR: merge developmaster).
  • Freeze develop; all future work branches off master.

🤖 Generated with Claude Code

Add build.yml running yarn build on push to master/release/** and PRs
to master. Convert deploy.yml to workflow_dispatch-only so publishing
to docs.flamingock.io is always a deliberate manual action with branch
selection (master, release/1.4, ...). Add RELEASE.md documenting the flow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant