Skip to content

πŸ”¨ 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

  1. Create features & fixes:

    • From dev, create branches like:
      • feat/login-redesign
      • fix/image-upload-bug
      • chore/version-upgrade
  2. Merge frequently to dev (via PRs):

    • PR reviewed β†’ merged into dev
    • dev always reflects "what we’re working on now"
  3. Promote to alpha regularly:

    • Merge dev β†’ alpha (e.g., weekly or bi-weekly cadence)
    • Tag & deploy alpha versions (e.g., v1.3.0-alpha.1)
  4. Stabilize for beta:

    • Once features are tested in alpha, promote from alpha β†’ beta
    • Tag & deploy beta versions (e.g., v1.3.0-beta.2)
  5. Cut main release:

    • After alpha and beta testing, merge beta β†’ main
    • Tag & deploy production version (e.g., v1.3.0)

πŸ“¦ 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

  1. Direct push to main branch, no features / no branches needed.

  2. When you are ready to deploy it via labs.visualli.ai URL, follow the instructions inside README.md of this repository.