parent
91172d6387
commit
f26880db03
4 changed files with 6 additions and 8 deletions
|
@ -86,10 +86,7 @@ A good commit message should describe what changed and why. The Electron project
|
|||
uses [semantic commit messages](https://conventionalcommits.org/) to streamline
|
||||
the release process.
|
||||
|
||||
Before a pull request can be merged, it should include at least one semantic
|
||||
commit message, though it's not necessary for all commits in the pull request
|
||||
to be semantic. Alternatively, you can **update your pull request title** to
|
||||
start with a semantic prefix.
|
||||
Before a pull request can be merged, it **must** have a pull request title with a semantic prefix.
|
||||
|
||||
Examples of commit messages with semantic prefixes:
|
||||
|
||||
|
@ -108,6 +105,7 @@ Common prefixes:
|
|||
- perf: A code change that improves performance
|
||||
- refactor: A code change that neither fixes a bug nor adds a feature
|
||||
- style: Changes that do not affect the meaning of the code (linting)
|
||||
- vendor: Bumping a dependency like libchromiumcontent or node
|
||||
|
||||
Other things to keep in mind when writing a commit message:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue