Add issue and pull request templates for Forgejo
Signed-off-by: nicole mikołajczyk <git@mkljczk.pl>
This commit is contained in:
parent
ec6ffa4fdf
commit
b798f7d6e9
2 changed files with 35 additions and 0 deletions
10
.forgejo/pull_request_template.md
Normal file
10
.forgejo/pull_request_template.md
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
### Checklist
|
||||
- [ ] Adding a changelog: In the `changelog.d` directory, create a file named `<code>.<type>`.
|
||||
|
||||
`<code>` can be anything, but we recommend using a more or less unique identifier to avoid collisions, such as the branch name.
|
||||
|
||||
`<type>` can be `add`, `change`, `remove`, `fix`, `security` or `skip`. `skip` is only used if there is no user-visible change in the PR (for example, only editing comments in the code). Otherwise, choose a type that corresponds to your change.
|
||||
|
||||
In the file, write the changelog entry. For example, if a PR adds group functionality, we can create a file named `group.add` and write `Add group functionality` in it.
|
||||
|
||||
If one changelog entry is not enough, you may add more. But that might mean you can split it into two PRs. Only use more than one changelog entry if you really need to (for example, when one change in the code fix two different bugs, or when refactoring).
|
||||
Loading…
Add table
Add a link
Reference in a new issue