|
| 1 | +# PR Creation Rules |
| 2 | +This document describes the format and rules for creating a Pull Request (PR) on GitHub. |
| 3 | + |
| 4 | +# Execution Details |
| 5 | +## Commit Guidelines |
| 6 | +- Use imperative mood for commit messages (e.g., "Fix bug" instead of "Fixed |
| 7 | +- Write Commit messages in English |
| 8 | + |
| 9 | +## PR Guidelines |
| 10 | +- If there are unstaged changes when creating a pull request, please split them appropriately and commit them separately. |
| 11 | +- When using the gh command, first authenticate with ```gh auth login```. |
| 12 | +- Use the [PR Template](../templates/PR_TEMPLATE.md) for PR descriptions |
| 13 | +- PR titles should be concise and descriptive |
| 14 | +- Ensure all tests pass before submitting a PR |
| 15 | +- Write PR title and descriptions in English |
| 16 | + |
| 17 | +## Command to Execute |
| 18 | + |
| 19 | +To create a PR, execute the following command. Add options as needed to construct the title, body, etc. |
| 20 | +```bash |
| 21 | +gh pr create |
| 22 | +``` |
| 23 | + |
| 24 | +The rules for describing the content of the PR are as follows. |
| 25 | +## Title |
| 26 | +Follow these rules for the PR title: |
| 27 | +- Write the title in English. |
| 28 | +- Keep the title concise and clearly indicate the changes. |
| 29 | + |
| 30 | +## Body |
| 31 | +Follow these rules for the PR body: |
| 32 | +- Write the body in English. |
| 33 | +- It is recommended to divide the body into the following sections: |
| 34 | + - Refer to the [PR Template](../templates/PR_TEMPLATE.md) for the PR body template. |
| 35 | +- Briefly explain the purpose and impact of the changes. |
| 36 | +- Include related issue numbers or ticket numbers, if possible. |
| 37 | + |
| 38 | +## Labels |
| 39 | +Labels are automatically assigned by GitHub Actions, so no manual configuration is required. |
0 commit comments