📄️ Repository
Our repository naming convention follows a lowercase slug case format for consistency and clarity. Whether it's a backend, frontend, mobile, desktop, or fullstack project, the naming convention remains consistent, making it easier to identify and manage repositories across our projects.
📄️ Branch
Our branching strategy ensures a clear and organized development process. We use main for production, dev for development, and staging for testing. Feature branches follow a username/feat/feature-name format, allowing for easy tracking and collaboration.
📄️ Commit
Our commit convention follows the Conventional Commits specification for clear and standardized commit messages. This convention ensures consistency and enables automated release notes generation and versioning.
📄️ Tagging & Release
Releases mark significant milestones in our project's development lifecycle. They typically include new features, bug fixes, and improvements packaged for deployment.