Skip to content

chore: adopt trunk based development on main - #669

Merged
fgmacedo merged 1 commit into
developfrom
fgmacedo/trunk-based-development
Oct 12, 2026
Merged

fgmacedo merged 1 commit into
developfrom
fgmacedo/trunk-based-development

Conversation

@fgmacedo

Copy link
Copy Markdown
Owner

What

Drops git-flow. main becomes the only long-lived branch, releases are tags on main, hotfixes come from release/X.Y.x branches cut from the released tag with fixes cherry-picked from main. The latest tag keeps moving on every release.

Changes

  • Workflows: Python checks and pages run on main (plus release/** pushes for hotfix CI); the Sonar-era git fetch origin develop step is removed from Python checks and release.
  • README: Codecov badge and images point at main; commits-since badge measures from the latest release and links compare/latest...main.
  • docs/conf.py: GitHub links use main.
  • docs/contributing.md: contributor branches start from main, release process rewritten without git-flow, new "Hotfix releases" section.
  • docs/installation.md: clone URL uses https:// (GitHub no longer serves git://).
  • AGENTS.md: git workflow section.

After merge (repo settings, done manually)

  1. Fast-forward main to develop.
  2. Default branch -> main; retarget feat: add event deferral to states #664.
  3. github-pages environment: allow main and v* tags, drop develop.
  4. Delete develop.
  5. Codecov default branch and ReadTheDocs latest follow main.

Drop the git-flow model: main is the only long-lived branch, releases are
tags on main and hotfixes come from release/X.Y.x branches cut from the
released tag. Point CI, badges, docs links and the contributing guide at
main and remove the Sonar-era 'git fetch origin develop' step.

Signed-off-by: Fernando Macedo <fgmacedo@gmail.com>
@sonarqubecloud

Copy link
Copy Markdown

@fgmacedo fgmacedo self-assigned this Oct 12, 2026
@fgmacedo
fgmacedo merged commit 3e3e599 into develop Oct 12, 2026
6 checks passed
@fgmacedo
fgmacedo deleted the fgmacedo/trunk-based-development branch October 12, 2026 15:30
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