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
Executing a lint pre-push hook is important for several reasons:
1. **Code Quality**: Ensures that all code being pushed meets the defined coding standards, improving overall code quality and consistency.
2. **Error Prevention**: Catches syntax errors and potential bugs early, reducing the likelihood of introducing issues into the shared codebase.
3. **Consistency**: Maintains a consistent code style across the team, making the codebase easier to read and maintain.
4. **Efficiency**: Automates the linting process, saving time for developers by catching issues before they reach code review or deployment stages.
5. **Continuous Integration**: Integrates seamlessly with continuous integration practices, ensuring that only clean, lint-free code enters the repository.
By enforcing linting at the pre-push stage, teams can maintain high standards of code quality and reduce the frequency of code issues, leading to more robust and maintainable software.
Copy file name to clipboardExpand all lines: README.md
+13
Original file line number
Diff line number
Diff line change
@@ -12,3 +12,16 @@ Habitica's code is licensed as described at https://github.com/HabitRPG/habitica
12
12
**Found a bug?** Please report it to [admin email](mailto:[email protected]) rather than creating an issue (an admin will advise you if a new issue is necessary; usually it is not).
13
13
14
14
**Have any questions about Habitica or its community?** See the links in the [habitica.com](https://habitica.com) website's Help menu or drop in to [Guilds > Tavern Chat](https://habitica.com/groups/tavern) to ask questions or chat socially!
15
+
16
+
17
+
### Setup git hooks
18
+
To improve code quality and rise feedback loop more efficient you can setup pre-push hooks.
19
+
Hook will execute eslint verification without fixing.
20
+
Eslint errors are restricted on pipeline level, so to reduce time for a feedback you can incorporate it in development stage.
21
+
#### Setup hook
22
+
From terminal/power shel execute script from
23
+
```
24
+
.\scripts\setup-pre-commit-scipts.sh
25
+
```
26
+
If you would like to skip pre-push hook you can push with additional parameter
0 commit comments