alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

[docs] Updating contribution guide for usage of [docs] prefix

Browse Source
This commit is contained in:
Gunnar Morling 2022-04-07 10:54:32 +02:00 committed by Vojtěch Juránek
parent 1e425b304b
commit ecdc43adcc
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTE.md
View File

@ -151,6 +151,14 @@ to the database and use logical decoding to read the transaction log. Several ne
integration test were added. integration test were added.
``` ```
As an exception, commits for trivial documentation changes which don't warrant the creation of a Jira issue can be prefixed with `[docs]`, for example:
```
[docs] Typo fix in Postgres connector documentation
```
The following commit message prefixes are reserved for internal usage by the Debezium CI infrastructure and should not be used in manually created commits: `[release]`, `[jenkins-jobs]`, `[maven-release-plugin]`, and `[ci]`.
### Code Formatting ### Code Formatting
This project utilizes a set of code style rules that are automatically applied by the build process. There are two ways in which you can apply these rules while contributing: This project utilizes a set of code style rules that are automatically applied by the build process. There are two ways in which you can apply these rules while contributing: