sigs.k8s.io/kueue@v0.6.2/.github/PULL_REQUEST_TEMPLATE.md (about)

     1  <!--  Thanks for sending a pull request!  Here are some tips for you:
     2  
     3  1. If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide/first-contribution.md#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
     4  2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here:
     5  https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
     6  3. Ensure you have added or ran the appropriate tests for your PR: https://git.k8s.io/community/contributors/devel/sig-testing/testing.md
     7  4. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
     8  5. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
     9  -->
    10  
    11  #### What type of PR is this?
    12  
    13  <!--
    14  Add one of the following kinds:
    15  /kind bug
    16  /kind cleanup
    17  /kind documentation
    18  /kind feature
    19  
    20  Optionally add one or more of the following kinds if applicable:
    21  /kind api-change
    22  /kind deprecation
    23  /kind failing-test
    24  /kind flake
    25  /kind regression
    26  -->
    27  
    28  #### What this PR does / why we need it:
    29  
    30  #### Which issue(s) this PR fixes:
    31  <!--
    32  *Automatically closes linked issue when PR is merged.
    33  Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
    34  _If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
    35  -->
    36  Fixes #
    37  
    38  #### Special notes for your reviewer:
    39  
    40  #### Does this PR introduce a user-facing change?
    41  <!--
    42  If no, just write "NONE" in the release-note block below.
    43  If yes, a release note is required:
    44  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".
    45  -->
    46  ```release-note
    47  
    48  ```