external
/
pg_stat_monitor
mirror of https://github.com/percona/pg_stat_monitor.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PG-457: added vim code annotation config example 

Signed-off-by: Kai Wagner <kai.wagner@percona.com>
pull/273/head
Kai Wagner 2022-06-28 08:56:12 +02:00
parent f73f3fec09
commit ebf940a3c0
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
CONTRIBUTING.md
View File

@ -42,6 +42,22 @@ If the bug hasn’t been reported / addressed, or we’ve agreed on the enhancem
2. Clone this repository on your machine. 2. Clone this repository on your machine.
3. Create a separate branch for your changes. If you work on a Jira issue, please include the issue number in the branch name so it reads as `<JIRAISSUE>-my_branch`. This makes it easier to track your contribution. 3. Create a separate branch for your changes. If you work on a Jira issue, please include the issue number in the branch name so it reads as `<JIRAISSUE>-my_branch`. This makes it easier to track your contribution.
4. Make your changes. Please follow the guidelines outlined in the [PostgreSQL Coding Standard](https://www.postgresql.org/docs/current/source.html) to improve code readability. 4. Make your changes. Please follow the guidelines outlined in the [PostgreSQL Coding Standard](https://www.postgresql.org/docs/current/source.html) to improve code readability.
<details>
<summary>.vimrc configuration example</summary>
```
set nocompatible " choose no compatibility with legacy vi
syntax enableset
tabstop=4set
background=lightset
textwidth=80set
colorcolumn=80
let g:filestyle_ignore_patterns = ['^\t* \{1,3}\S']
highlight Normal ctermbg=15
highlight ColorColumn ctermbg=52
```
</details>
5. Test your changes locally. See the [Running tests ](#running-tests) section for more information 5. Test your changes locally. See the [Running tests ](#running-tests) section for more information
6. Update the documentation describing your changes. See the [Contributing to documentation](#contributing-to-documentation) section for details 6. Update the documentation describing your changes. See the [Contributing to documentation](#contributing-to-documentation) section for details
8. Commit the changes. Add the Jira issue number at the beginning of your message subject, so that is reads as `<JIRAISSUE> : My commit message`. Follow this pattern for your commits: 8. Commit the changes. Add the Jira issue number at the beginning of your message subject, so that is reads as `<JIRAISSUE> : My commit message`. Follow this pattern for your commits: