This is an automated email from the ASF dual-hosted git repository.
sajjad pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pinot.git
The following commit(s) were added to refs/heads/master by this push:
new e986d00548 Make the PR template simpler (#8455)
e986d00548 is described below
commit e986d00548cfb2e8c25770c19f3fce076d9ef49b
Author: Sajjad Moradi <moradi.saj...@gmail.com>
AuthorDate: Fri Apr 8 10:47:31 2022 -0700
Make the PR template simpler (#8455)
---
.github/PULL_REQUEST_TEMPLATE.md | 47 +++++++++++++++++++---------------------
1 file changed, 22 insertions(+), 25 deletions(-)
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 350c8399f3..7525faa268 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,30 +1,27 @@
-## Description
-<!-- Add a description of your PR here.
-A good description should include pointers to an issue or design document, etc.
--->
-## Upgrade Notes
-Does this PR prevent a zero down-time upgrade? (Assume upgrade order:
Controller, Broker, Server, Minion)
-* [ ] Yes (Please label as **<code>backward-incompat</code>**, and complete
the section below on Release Notes)
+Instructions:
+1. The PR has to be tagged with at least one of the following labels (*):
+ 1. `feature`
+ 2. `bugfix`
+ 3. `performance`
+ 4. `ui`
+ 5. `backward-incompat`
+ 6. `release-notes` (**)
+2. Remove these instructions before publishing the PR.
+
+(*) Other labels to consider:
+- `testing`
+- `dependencies`
+- `docker`
+- `kubernetes`
+- `observability`
+- `security`
+- `code-style`
+- `extension-point`
+- `refactor`
+- `cleanup`
-Does this PR fix a zero-downtime upgrade introduced earlier?
-* [ ] Yes (Please label this as **<code>backward-incompat</code>**, and
complete the section below on Release Notes)
-
-Does this PR otherwise need attention when creating release notes? Things to
consider:
+(**) Use `release-notes` label for scenarios like:
- New configuration options
- Deprecation of configurations
- Signature changes to public methods/interfaces
- New plugins added or old plugins removed
-* [ ] Yes (Please label this PR as **<code>release-notes</code>** and complete
the section on Release Notes)
-## Release Notes
-<!-- If you have tagged this as either backward-incompat or release-notes,
-you MUST add text here that you would like to see appear in release notes of
the
-next release. -->
-
-<!-- If you have a series of commits adding or enabling a feature, then
-add this section only in final commit that marks the feature completed.
-Refer to earlier release notes to see examples of text.
--->
-## Documentation
-<!-- If you have introduced a new feature or configuration, please add it to
the documentation as well.
-See
https://docs.pinot.apache.org/developers/developers-and-contributors/update-document
--->
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
