docs: update the PR template with better areas

Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com>
This commit is contained in:
Leonardo Di Donato
2019-09-16 03:59:57 +02:00
committed by Lorenzo Fontana
parent 34654fd753
commit 6833d8a022

View File

@@ -2,8 +2,8 @@
1. If this is your first time, please read our contributor guidelines in the [CONTRIBUTING.md](CONTRIBUTING.md) file and learn how to compile Falco from source [here](https://falco.org/docs/source). 1. If this is your first time, please read our contributor guidelines in the [CONTRIBUTING.md](CONTRIBUTING.md) file and learn how to compile Falco from source [here](https://falco.org/docs/source).
2. Please label this pull request according to what type of issue you are addressing. 2. Please label this pull request according to what type of issue you are addressing.
5. Please add a release note! 3. . Please add a release note!
6. If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature" 4. If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature"
--> -->
**What type of PR is this?** **What type of PR is this?**
@@ -30,19 +30,29 @@
> /kind rule-create > /kind rule-create
<!--
Please remove the leading whitespace before the `/kind <>` you uncommented.
-->
**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: > Uncomment one (or more) `/area <>` lines:
> /area build
> /area engine > /area engine
> /area examples
> /area rules > /area rules
> /area deployment
> /area integrations > /area integrations
> /area examples > /area tests
<!--
Please remove the leading whitespace before the `/area <>` you uncommented.
-->
**What this PR does / why we need it**: **What this PR does / why we need it**:
@@ -63,7 +73,8 @@ Fixes #
<!-- <!--
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, prepend 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`.
--> -->