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
+43Lines changed: 43 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,49 @@ To build the ECD module from source, follow these steps:
49
49
50
50
- Open your browser and navigate to http://localhost:8080/swagger-ui.html#!/
51
51
52
+
## Setting Up Commit Hooks
53
+
54
+
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:
55
+
56
+
### Prerequisites
57
+
- Node.js (v14 or later)
58
+
- npm (comes with Node.js)
59
+
60
+
### Setup Steps
61
+
62
+
1.**Install Node.js and npm**
63
+
- Download and install from [nodejs.org](https://nodejs.org/)
64
+
- Verify installation with:
65
+
```
66
+
node --version
67
+
npm --version
68
+
```
69
+
2. **Install dependencies**
70
+
- From the project root directory, run:
71
+
```
72
+
npm ci
73
+
```
74
+
- This will install all required dependencies including Husky and commitlint
75
+
3. **Verify hooks installation**
76
+
- The hooks should be automatically installed by Husky
77
+
- You can verify by checking if the `.husky` directory contains executable hooks
78
+
### Commit Message Convention
79
+
This project follows a specific commit message format:
80
+
- Format: `type(scope): subject`
81
+
- Example: `feat(login): add remember me functionality`
82
+
Types include:
83
+
- `feat`: A new feature
84
+
- `fix`: A bug fix
85
+
- `docs`: Documentation changes
86
+
- `style`: Code style changes (formatting, etc.)
87
+
- `refactor`: Code changes that neither fix bugs nor add features
88
+
- `perf`: Performance improvements
89
+
- `test`: Adding or fixing tests
90
+
- `build`: Changes to build process or tools
91
+
- `ci`: Changes to CI configuration
92
+
- `chore`: Other changes (e.g., maintenance tasks, dependencies)
93
+
Your commit messages will be automatically validated when you commit, ensuring project consistency.
94
+
52
95
## Filing Issues
53
96
54
97
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