mirrors/conventionalcommits.org
0
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2025-08-22 13:58:35 +00:00
Code

fix: fix grammatical error (#145)

Browse Source
This commit is contained in:
Nathan Woltman 2019-04-22 12:59:52 -04:00 committed by Benjamin E. Coe
parent 44ec849bb0
commit 524fbca542
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/next/index.md
View File

@ -150,7 +150,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers.
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About

2
content/v1.0.0-beta.1/index.md
View File

@ -130,7 +130,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About

2
content/v1.0.0-beta.2/index.md
View File

@ -155,7 +155,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About

2
content/v1.0.0-beta.3/index.md
View File

@ -139,7 +139,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers.
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About

2
content/v1.0.0-beta.4/index.md
View File

@ -151,7 +151,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers.
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About

2
content/v1.0.0-beta/index.md
View File

@ -130,7 +130,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About