You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,36 @@ Here are some ways you can contribute to the project:
22
22
6.**Push** your branch to your GitHub repository: `git push origin feature-name`.
23
23
7. Create a **Pull Request (PR)** from your branch to the original repository's `main` or `master` branch.
24
24
25
+
## Commit Message Format
26
+
27
+
We follow the conventional commit message format using Commitlint to ensure consistent and meaningful commit messages. This format helps in automated versioning and release notes generation.
28
+
29
+
### Commit Types
30
+
31
+
-**feat:** A new feature for the user or a significant change.
32
+
-**fix:** A bug fix for the user or a significant issue resolution.
33
+
-**docs:** Documentation changes.
34
+
-**chore:** Routine tasks, maintenance, or tooling changes.
35
+
36
+
### How to Write Commit Messages
37
+
38
+
- Start the commit message with the type, followed by a colon and a space (e.g., `feat: Add new feature`).
39
+
- Provide a concise and descriptive commit message.
40
+
- If the commit addresses an issue, include the issue number in the message (e.g., `fix: Resolve #123`).
41
+
42
+
### Example Commit Messages
43
+
44
+
- feat: Implement user authentication
45
+
- fix: Resolve issue #456 with data validation
46
+
- docs: Update installation instructions
47
+
- chore: Upgrade dependencies to latest versions
48
+
49
+
### Commitlint Configuration
50
+
51
+
We use Commitlint to enforce the commit message format. Ensure that your commits adhere to the specified format. You can find the Commitlint configuration in the repository.
52
+
53
+
For more details on Commitlint and conventional commits, please refer to [Commitlint Documentation](https://commitlint.js.org/).
54
+
25
55
## Pull Request Guidelines
26
56
27
57
- Make sure your PR addresses an issue or feature request.
0 commit comments