github/falco
1
0
Fork 0
mirror of https://github.com/falcosecurity/falco.git synced 2025-06-24 22:02:19 +00:00
Code Issues Projects Releases Wiki Activity

update(.github): PR template

Browse Source 
Some refinements and improvements to the GitHub PR template.

Co-authored-by: Lorenzo Fontana <lo@linux.com>
Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com>
This commit is contained in:
Leo Di Donato 2019-07-01 12:37:03 +02:00 committed by Lorenzo Fontana
parent 48f2b1d08a
commit fade424120
1 changed files with 22 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -7,48 +7,66 @@
--> -->
**What type of PR is this?** **What type of PR is this?**
> Uncomment only one ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespaces from that line:
> > Uncomment one (or more) `/kind <>` lines:
> /kind bug > /kind bug
> /kind cleanup > /kind cleanup
> /kind design > /kind design
> /kind documentation > /kind documentation
> /kind failing-test > /kind failing-test
> /kind feature > /kind feature
> /kind flaky-test > /kind flaky-test
> If contributing rules or changes to rules, please make sure to uncomment the appropriate kind > If contributing rules or changes to rules, please make sure to also uncomment one of the following line:
> /kind rule-update > /kind rule-update
> /kind rule-create > /kind rule-create
**Any specific area of the project related to this PR?** **Any specific area of the project related to this PR?**
> Uncomment one (or more) `/area <>` lines:
> /area engine > /area engine
> /area rules > /area rules
> /area deployment > /area deployment
> /area integrations > /area integrations
> /area examples > /area examples
**What this PR does / why we need it**: **What this PR does / why we need it**:
**Which issue(s) this PR fixes**: **Which issue(s) this PR fixes**:
<!-- <!--
Automatically closes linked issue when PR is merged. Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
If PR is `kind/failing-tests` or `kind/flaky-test`, please post the related issues/tests in a comment and do not use `Fixes`. If PR is `kind/failing-tests` or `kind/flaky-test`, please post the related issues/tests in a comment and do not use `Fixes`.
--> -->
Fixes # Fixes #
**Special notes for your reviewer**: **Special notes for your reviewer**:
**Does this PR introduce a user-facing change?**: **Does this PR introduce a user-facing change?**:
<!-- <!--
If no, just write "NONE" in the release-note block below. If no, just write "NONE" in the release-note block below.
If yes, a release note is required: If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required:". Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, prepend the string "action required:".
For example, `action required: change the API interface of the rule engine`. For example, `action required: change the API interface of the rule engine`.
--> -->
```release-note ```release-note
``` ```