Skip to content

Latest commit

 

History

History
32 lines (24 loc) · 1.03 KB

File metadata and controls

32 lines (24 loc) · 1.03 KB

Commit Guidelines

When contributing to this repository, please follow these guidelines to ensure a smooth and efficient collaboration process.

Conventional Commits

Use the Conventional Commits specification for commit messages. This helps maintain a clear and consistent commit history.

  • Commit message must be in English.
  • Use present tense and an imperative mode.
  • Include a scope to specify the area of the codebase that is affected by the commit (optional but recommended).
  • You can use the following types of commits:
    • feat: A new feature.
    • fix: A bug fix.
    • docs: Documentation changes.
    • refactor: Code refactoring without changing functionality.
    • test: Adding or updating tests.
    • chore: Changes to the build process or auxiliary tools and libraries.

Example Commit Message

feat(auth): add jwt authentication.
fix(auth): resolve issue with user registration endpoint.
docs: update README with installation instructions.