docs: add missing heading to commit message section (#8079)
This commit is contained in:
@@ -20,6 +20,7 @@
|
|||||||
- [Parse Error](#parse-error)
|
- [Parse Error](#parse-error)
|
||||||
- [Parse Server Configuration](#parse-server-configuration)
|
- [Parse Server Configuration](#parse-server-configuration)
|
||||||
- [Pull Request](#pull-request)
|
- [Pull Request](#pull-request)
|
||||||
|
- [Commit Message](#commit-message)
|
||||||
- [Breaking Change](#breaking-change)
|
- [Breaking Change](#breaking-change)
|
||||||
- [Merging](#merging)
|
- [Merging](#merging)
|
||||||
- [Breaking Change](#breaking-change-1)
|
- [Breaking Change](#breaking-change-1)
|
||||||
@@ -305,6 +306,8 @@ Introducing new [Parse Server configuration][config] parameters requires the fol
|
|||||||
|
|
||||||
## Pull Request
|
## Pull Request
|
||||||
|
|
||||||
|
### Commit Message
|
||||||
|
|
||||||
For release automation, the title of pull requests needs to be written in a defined syntax. We loosely follow the [Conventional Commits](https://www.conventionalcommits.org) specification, which defines this syntax:
|
For release automation, the title of pull requests needs to be written in a defined syntax. We loosely follow the [Conventional Commits](https://www.conventionalcommits.org) specification, which defines this syntax:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|||||||
Reference in New Issue
Block a user