Skip to content

Commit 4a58a8e

Browse files
Merge pull request #96 from praliptarajoo/contributing-update
Contributing update
2 parents 96779b6 + 2f1eebb commit 4a58a8e

File tree

3 files changed

+38
-6
lines changed

3 files changed

+38
-6
lines changed

.github/workflows/ci.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,8 @@ jobs:
6868
create-github-release:
6969
name: Create Github release document
7070
runs-on: ubuntu-latest
71+
permissions:
72+
contents: write
7173
needs: build
7274
steps:
7375
- name: Checkout code

CONTRIBUTING.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,36 @@ Here are some ways you can contribute to the project:
2222
6. **Push** your branch to your GitHub repository: `git push origin feature-name`.
2323
7. Create a **Pull Request (PR)** from your branch to the original repository's `main` or `master` branch.
2424

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+
2555
## Pull Request Guidelines
2656

2757
- Make sure your PR addresses an issue or feature request.

tsconfig.json

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,19 +15,19 @@
1515
"incremental": true,
1616
"plugins": [
1717
{
18-
"name": "next"
19-
}
18+
"name": "next",
19+
},
2020
],
2121
"paths": {
22-
"@/*": ["./src/*"]
23-
}
22+
"@/*": ["./src/*"],
23+
},
2424
},
2525
"include": [
2626
"next-env.d.ts",
2727
"**/*.ts",
2828
"**/*.tsx",
2929
".next/types/**/*.ts",
30-
"build/types/**/*.ts"
30+
"build/types/**/*.ts",
3131
],
32-
"exclude": ["node_modules"]
32+
"exclude": ["node_modules"],
3333
}

0 commit comments

Comments
 (0)