fullstackhero

Guide

Overview

Help shape fullstackhero — branching model, issues, PRs, and conventions.

views 0 Last updated

Contributing

See the repo’s CONTRIBUTING.md for the latest guidelines.

Branching model

The repo uses a single long-lived branch: main (the default). There is no develop branch.

  • Branch from and target main. Open your feature/fix branch off the latest main and point your PR back at main.
  • Releases are tags, not a branch. Stable releases are cut from v* tags (e.g. v10.0.0); “latest stable” is the newest tag/GitHub Release, and main stays releasable. Older majors, if maintained, live on short-lived release/x.y branches.
  • CI gates the merge. A PR must pass the Backend CI and/or Frontend CI checks (whichever your change touches — see CI/CD) before it can merge.