π¨ Development Workflow¶
Repo: visualli.ai¶
π Branches¶
| Branch | Purpose | URL | Stability | Audience |
|---|---|---|---|---|
dev |
Developersβ playground | https://dev.visualli.ai | π΄ Low | Visualli crew |
alpha |
Early access / bleeding edge | https://alpha.visualli.ai | π Medium | Select userbase |
beta |
Pre-release candidate | π‘ High | Broad userbase | |
main |
Production release | π’ Very high | All users |
dev β main integration branch for all features/bugfixes
βββ feat/awesome-feature
βββ fix/some-bug
βββ chore/update-config
β
βΌ
alpha β early testing / bleeding-edge features
β
βΌ
beta β stable preview / pre-release testing
β
βΌ
main β production-ready stable release
β Flow¶
-
Create features & fixes:
- From
dev, create branches like:feat/login-redesignfix/image-upload-bugchore/version-upgrade
- From
-
Merge frequently to
dev(via PRs):- PR reviewed β merged into dev
devalways reflects "what weβre working on now"
-
Promote to
alpharegularly:- Merge
devβalpha(e.g., weekly or bi-weekly cadence) - Tag & deploy
alphaversions (e.g., v1.3.0-alpha.1)
- Merge
-
Stabilize for
beta:- Once features are tested in
alpha, promote fromalphaβbeta - Tag & deploy
betaversions (e.g., v1.3.0-beta.2)
- Once features are tested in
-
Cut
mainrelease:- After alpha and beta testing, merge
betaβmain - Tag & deploy
productionversion (e.g., v1.3.0)
- After alpha and beta testing, merge
π¦ Versioning¶
- Use Semantic Versioning: v1.2.3-alpha.1, v1.2.3-beta.2, v1.2.3
Repo: visualli-labs¶
π Branches¶
| Branch | Purpose | URL | Stability | Audience |
|---|---|---|---|---|
main |
Developersβ playground | https://labs.visualli.ai | π΄ Low | Visualli crew |
β Flow¶
-
Direct push to
mainbranch, no features / no branches needed. -
When you are ready to deploy it via labs.visualli.ai URL, follow the instructions inside
README.mdof this repository.