ci: migrate to trunk-based development - #581
Merged
Merged
Conversation
Replace the gitflow pipeline (cicd.yml) with a trunk-based setup: - ci.yml: PR validation (build + internal link check) and Firebase preview channel per pull request - deploy-production.yml: every push to main builds and deploys to production, with workflow_dispatch as manual redeploy/rollback escape hatch; deploy no longer depends on the release job - semantic-release slimmed down to commit-analyzer, release-notes-generator and github plugins — no more chore(release) commit-back, version bump or CHANGELOG.md writes; CHANGELOG.md is frozen in favor of GitHub Releases - fix repository.url (move4mobile -> move-frontend), the cause of the EGITNOPERMISSION failure in the last release run - dependabot: weekly grouped updates against main per the discipline standard (cooldown, eleventy/release-tools groups, github-actions ecosystem); integration/dependabot funnel retired - codeql: develop references replaced by main - docs updated to describe the trunk-based branch model
Michael (mschilling)
temporarily deployed
to
Preview Channels
July 5, 2026 14:00 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
|
Visit the preview URL for this PR (updated for commit ad9f654): https://m4m-geekbites-dev--pr581-feat-trunk-based-ci-atsclmgp.web.app (expires Sun, 12 Jul 2026 14:00:46 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 995f16c8ca726a359e48b7c460e5b3e3ea21476d |
2 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
1 participant
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.
What
Migrates Geekbites from gitflow (
develop+main) to trunk-based development. After this PR merges,mainbecomes the default branch anddevelop+integration/dependabotwill be deleted.Why
DeployProductiondepended onCreateRelease, so a main merge with onlybuild/chorecommits produced no release and therefore no production deploy (happened on Next release #500 and again on Next release #549).EGITNOPERMISSION:package.json → repository.urlstill pointed at the oldmove4mobileorg.Changes
ci.yml(new)deploy-production.yml(new, replacescicd.yml)main→ build → deploy to production.workflow_dispatchas manual redeploy/rollback escape hatch. Deploy no longer depends on the release jobcommit-analyzer+release-notes-generator+github. No morechore(release)commit-back, version bumps or CHANGELOG writes.CHANGELOG.mdfrozen in favor of GitHub Releasespackage.jsonrepository.url/bugs/homepage→move-frontend(fixes the release failure)mainper the frontend discipline standard (cooldown,eleventy/release-tools/github-actionsgroups).integration/dependabotfunnel retireddevelopreferences →mainFollow-up (repo settings, after merge)
maindevelop+integration/dependabotproductionenvironment deployment branch policy (release/production→main)Test plan
npm run buildsucceeds locally (Node 24)npm run check-broken-links:internal— 0 broken