trpc.group/trpc-go/trpc-go@v1.0.3/.github/PULL_REQUEST_TEMPLATE.md (about)

     1  <!-- Thanks for your PR, you're awesome! 👍
     2  
     3  Please ensure you have read the [Contributing code](https://github.com/trpc-group/trpc-go/blob/main/CONTRIBUTING.md#contributing-code). 
     4  
     5  The PR title should be formatted as follows: `client: remove internal info`
     6    - The package name goes before the colon
     7    - The part after the colon uses the verb tense + phrase that completes the blank in,
     8      "This change modifies tRPC-Go to ___________"
     9    - Lowercase verb after the colon
    10    - No trailing period
    11    - Keep the title as short as possible. ideally under 76 characters or shorter.
    12  
    13  Add one of the following type of label:
    14  type/bug: Fixes a newly discovered bug.
    15  type/enhancement: Adding tests, refactoring.
    16  type/feature: New functionality.
    17  type/documentation: Adds documentation.
    18  
    19  Optionally add any of the following type of label if applicable:
    20  type/api-change: Adds, removes, or changes an API.
    21  type/failing-test: CI test case is showing intermittent failures.
    22  type/performance: Changes that improves performance.
    23  type/ci: Changes the CI configuration files and scripts.
    24  -->
    25  
    26  <!--
    27  *Automatically closes linked issue when PR is merged.
    28  Usage: `Fixes #<issue number>`.
    29  -->
    30  Fixes #
    31  
    32  <!--
    33  Does this PR introduce a user-facing change?
    34  
    35  If no, just write "NONE" below.
    36  If yes, a release note is required, Enter your extended release note below.
    37  
    38  A release note needs a clear, concise description of the change. 
    39  -->
    40  RELEASE NOTES: NONE