chore: add '/kind sync` to PR template#2700
Conversation
Signed-off-by: Leonardo Di Giovanna <leonardodigiovanna1@gmail.com>
|
@ekoops: The provided milestone is not valid for this repository. Milestones in this repository: [ Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Wrong milestone /milestone 0.23.0 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2700 +/- ##
=======================================
Coverage 77.62% 77.62%
=======================================
Files 294 294
Lines 31951 31951
Branches 4716 4716
=======================================
Hits 24802 24802
Misses 7149 7149
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ekoops, irozzo-1A The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area CI
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This PR adds the `/kind sync" to the kind of PR a contributor can open.
This new kind is intended for all contributors who want to sync a branch with changes coming from another branch. This should be primarily used during the release processing, while syncing the release branch with changes cherry-picked from the master branch. Besides introducing the kind in the template, automation should also be updated in order support the new kind.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/milestone 0.22.0
Does this PR introduce a user-facing change?: