Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Update CONTRIBUTING.md - small typo fix #100

Merged
merged 1 commit into from
Sep 26, 2024
Merged

fix: Update CONTRIBUTING.md - small typo fix #100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,7 +221,7 @@ The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is opti

##### Type

Must classify commit to the certain type. Some of he examples of good types to use:
Must classify commit to the certain type. Some of the examples of good types to use:

* **build**: Changes that affect the build system or external dependencies
* **ci**: Changes to our CI configuration files and scripts
Expand Down Expand Up @@ -299,4 +299,4 @@ If the commit reverts a previous commit, it should begin with `revert: `, follow
The content of the commit message body should contain:

- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
- a clear description of the reason for reverting the commit message.
- a clear description of the reason for reverting the commit message.
Loading