File: PULL_REQUEST_TEMPLATE.md

package info (click to toggle)
insighttoolkit4 4.13.0-dfsg1-2~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 456,164 kB
  • sloc: cpp: 557,277; ansic: 146,850; fortran: 34,788; python: 16,543; sh: 2,187; lisp: 2,070; tcl: 993; java: 362; perl: 200; makefile: 123; csh: 81; pascal: 69; xml: 19; ruby: 10
file content (21 lines) | stat: -rw-r--r-- 1,083 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
See the [CONTRIBUTING](CONTRIBUTING.md) guide. Specifically:

Start ITK commit messages with a standard prefix (and a space):

 * BUG: fix for runtime crash or incorrect result
 * COMP: compiler error or warning fix
 * DOC: documentation change
 * ENH: new functionality
 * PERF: performance improvement
 * STYLE: no logic impact (indentation, comments)
 * WIP: Work In Progress not ready for merge

Provide a short, meaningful message that describes the change you made.

When the PR is based on a single commit, the commit message is usually left as the PR message.

A [reference to a related issue or pull request](https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. You can automatically [close a related issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/)

[@mentions](https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.

Thanks for contributing to ITK!