sigs.k8s.io/gateway-api@v1.0.0/.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 contributing to Gateway API, please read our
     4     developer guide (https://gateway-api.sigs.k8s.io/contributing/devguide/)
     5     and our community page (https://gateway-api.sigs.k8s.io/contributing/).
     6  2. If this is your first time contributing to a Kubernetes project, please read
     7     our contributor guidelines:
     8     https://git.k8s.io/community/contributors/guide/first-contribution.md#your-first-contribution
     9  3. Please label this pull request according to what type of issue you are
    10     addressing, especially if this is a release targeted pull request. For
    11     reference on required PR/issue labels, read here:
    12     https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
    13  4. If you want *faster* PR reviews, read how:
    14     https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
    15  5. If the PR is unfinished, see how to mark it:
    16     https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
    17  6. If this PR includes a new GEP please make sure you've followed the process
    18     outlined in our GEP overview, as this will help the community to ensure the
    19     best chance of positive outcomes for your proposal:
    20     https://gateway-api.sigs.k8s.io/geps/overview/#process
    21  -->
    22  
    23  **What type of PR is this?**
    24  <!--
    25  Add one of the following kinds:
    26  /kind bug
    27  /kind cleanup
    28  /kind documentation
    29  /kind feature
    30  /kind gep
    31  /kind test
    32  
    33  Optionally add one or more of the following kinds if applicable:
    34  /kind deprecation
    35  /kind failing-test
    36  /kind flake
    37  /kind regression
    38  /area conformance
    39  -->
    40  
    41  **What this PR does / why we need it**:
    42  
    43  **Which issue(s) this PR fixes**:
    44  <!--
    45  *Automatically closes linked issue when PR is merged.
    46  Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
    47  -->
    48  Fixes #
    49  
    50  **Does this PR introduce a user-facing change?**:
    51  <!--
    52  If no, just write "NONE" in the release-note block below.
    53  If yes, please enter a release note below:
    54  -->
    55  ```release-note
    56  
    57  ```