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: README.md
+50-1Lines changed: 50 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,10 +22,59 @@ Detailed information on API endpoints can be found in the [API Guide](https://pi
22
22
23
23
## Usage
24
24
All features have been exposed as REST endpoints. Refer to the SWAGGER API specification for details.
25
+
26
+
## Setting Up Commit Hooks
27
+
28
+
This project uses Git hooks to enforce consistent code quality and commit message standards. Even though this is a Java project, the hooks are powered by Node.js. Follow these steps to set up the hooks locally:
29
+
30
+
### Prerequisites
31
+
- Node.js (v14 or later)
32
+
- npm (comes with Node.js)
33
+
34
+
### Setup Steps
35
+
36
+
1.**Install Node.js and npm**
37
+
- Download and install from [nodejs.org](https://nodejs.org/)
38
+
- Verify installation with:
39
+
```
40
+
node --version
41
+
npm --version
42
+
```
43
+
44
+
2. **Install dependencies**
45
+
- From the project root directory, run:
46
+
```
47
+
npm ci
48
+
```
49
+
- This will install all required dependencies including Husky and commitlint
50
+
51
+
3. **Verify hooks installation**
52
+
- The hooks should be automatically installed by Husky
53
+
- You can verify by checking if the `.husky` directory contains executable hooks
54
+
55
+
### Commit Message Convention
56
+
57
+
This project follows a specific commit message format:
58
+
- Format: `type(scope): subject`
59
+
- Example: `feat(login): add remember me functionality`
60
+
61
+
Types include:
62
+
- `feat`: A new feature
63
+
- `fix`: A bug fix
64
+
- `docs`: Documentation changes
65
+
- `style`: Code style changes (formatting, etc.)
66
+
- `refactor`: Code changes that neither fix bugs nor add features
67
+
- `perf`: Performance improvements
68
+
- `test`: Adding or fixing tests
69
+
- `build`: Changes to build process or tools
70
+
- `ci`: Changes to CI configuration
71
+
- `chore`: Other changes (e.g., maintenance tasks, dependencies)
72
+
73
+
Your commit messages will be automatically validated when you commit, ensuring project consistency.
25
74
26
75
## Filing Issues
27
76
28
-
If you encounter any issues, bugs, or have feature requests, please file them in the [main AMRIT repository](https://github.com/PSMRI/AMRIT/issues). Centralizing all feedback helps us streamline improvements and address concerns efficiently.
77
+
If you encounter any issues, bugs, or have feature requests, please file them in the [main AMRIT repository](https://github.com/PSMRI/AMRIT/issues). Centralizing all feedback helps us streamline improvements and address concerns efficiently.
0 commit comments