-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
merge: merge branch "development" to "main"
CONTRIBUTING.md actualization
- Loading branch information
Showing
1 changed file
with
12 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,16 @@ | ||
# Contributing | ||
Rules of contributing to our project. | ||
1. If you want to add your own feature or fix something in our code, please create your own branch to do it. | ||
2. Please avoid verbs in commits' names ("project initialization" instead of "initialize project" or "initialized project") | ||
3. Once your branch is complete, you can make a pull request and wait for it to be reviewed. | ||
4. Description of pull request is required to be written. | ||
5. Your commits and pull requests must be named and described in English. | ||
6. Your naming of commits and pull requests must be logical and reasonable. Use conventional commits, please. | ||
7. Please use "git commit -s" option. | ||
8. If you are in doubt what to do, it's better to text developers. | ||
2. Enable precommit hooks using | ||
```shell | ||
git config --local core.hooksPath .githooks/ | ||
``` | ||
3. Use conventional commits, please. | ||
4. Please avoid verbs in commits' names ("project initialization" instead of "initialize project" or "initialized project") | ||
5. Once your branch is complete, you can make a pull request and wait for it to be reviewed. | ||
6. Description of pull request is required to be written. | ||
7. Your commits and pull requests must be named and described in English. | ||
8. Your naming of commits and pull requests must be logical and reasonable. | ||
9. Please use "git commit -s" option. | ||
10. If you are in doubt what to do, it's better to text developers. | ||
|