Repository files navigation

To ensure a clean, scalable, and team-friendly development workflow, UnifiedBits follows a consistent branching strategy using base and working branches.

• 🔒Production-ready branch
• Always contains the lateststable release
• Direct changes are restricted; merged only through pull requests (usually fromdev)

• 🚧Primary development branch
• All new features and fixes are merged intodev first
• Acts as a staging area before pushing to production (main)
• Frequently rebased or updated frommain to stay in sync

Always follow this structure when naming your branches:

<branch-type>/<domain>-<short-description>

Use lowercase letters and hyphens for readability.

feature/auth-add-otp-loginfix/ui-fix-navbar-overlaprefactor/api-cleanup-old-endpointsdocs/readme-update-api-usagetest/dashboard-add-user-metrics-tests

🛑Always create your branch from the latestdev branch to ensure you're working with the most recent code.

1. Checkout and pull the latestdev:

   git checkout devgit pull origin dev

2. Create your new branch fromdev:

   git checkout -b feature/ui-add-sidebar

3. Work on your feature/fix and commit usingConventional Commits:

   feat(ui): add collapsible sidebar component

4. Push your branch:

   git push origin feature/ui-add-sidebar

5. Open a Pull Request todev for review.

6. ✅ Once reviewed and tested, maintainers will mergedev intomain when ready for production.

• Syncdev regularly withmain
• Delete local and remote feature branches after merge
• Never commit directly tomain ordev unless it's critical (viahotfix/)

• 🔗UnifiedBits Commit Guidelines.
• 📘GitHub Flow vs Git Flow

“Organized branches mean faster development and cleaner launches.” — UnifiedBits

Let’s branch smartly and build boldly! 🚀