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

docs: fix missing period at the end of a sentence #218

Merged
merged 2 commits into from
Jan 16, 2025
Merged

docs: fix missing period at the end of a sentence #218

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
86d9765
docs: fix missing period at the end of a entence
Jan 15, 2025
4a27833
Merge branch 'main' into docs/addPeriodForSentence
jacobtrombetta Jan 16, 2025
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
10 changes: 5 additions & 5 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ When you contribute code, you affirm that the contribution is your original work

## <a name="style"></a> Style Guidelines

See [style guide](STYLE.md)
See [style guide](STYLE.md).

## <a name="submit"></a> Submission Guidelines

Expand Down Expand Up @@ -281,7 +281,7 @@ Must be one of the following:
* **perf!**: A code change that improves performance and introduces breaking changes (this correlates with MAJOR in Semantic Versioning).
* **refactor**: A code change that neither fixes a bug nor adds a feature (this correlates with a PATCH in Semantic Versioning).
* **refactor!**: A code change that neither fixes a bug nor adds a feature and introduces breaking changes (this correlates with MAJOR in Semantic Versioning).
* **test**: Adding missing tests or correcting existing tests
* **test**: Adding missing tests or correcting existing tests.
* **bench**: Adding missing benchmarks or correcting existing benchmarks (this does not correlate with any semantic versioning update).
* **build**: Changes that affect the build system or external dependencies (this correlates with a PATCH in Semantic Versioning).
* **ci**: Changes to our CI configuration files and scripts.
Expand All @@ -295,9 +295,9 @@ Try to not fill your commit with many unrelated changes to your code, as it make

Use the summary field to provide a succinct description of the change (less than 80 characters):

* use the imperative, present tense: "change", not "changing", nor "changed", and nor "changes"
* don't capitalize the first letter
* no dot (.) at the end
* use the imperative, present tense: "change", not "changing", nor "changed", and nor "changes".
* don't capitalize the first letter.
* no dot (.) at the end.

### <a name="commit-body"></a>Commit Message Body

Expand Down