version control rules - jamongx/twitter-clone GitHub Wiki

Branching Strategy:

  • The types of branches to be used.
- I use a feature branching model.
  • The role and purpose of each branch.
- The main branch contains the latest stable version of the project.
- Feature branches: feature/your-feature-name
- Bugfix branches: fix/your-fix-name

Tagging Strategy:

  • Procedures for creating and managing tags.
  • Naming conventions for tags.

Release Management:

  • The cycle and management process of releases.
  • Naming conventions for release versions.

Merging Strategy:

  • When and how to perform merges.
  • Handling procedures in cases where code review and testing are required.

Commit Policy:

Minimum unit and frequency of commits.

Commit Rule

1. Create a new branch.
2. Make your changes.
3. Commit your changes following our commit message format
4. Push your changes to your fork.
5. Open a pull request.

Format of commit messages.

<type>(<scope>): <description>
  • Types: feat, fix, docs, style, refactor, test, chore
  • Scope: Optional. Specifies the area of the project affected by the commit.
  • Description: Brief description of changes.
⚠️ **GitHub.com Fallback** ⚠️