summaryrefslogtreecommitdiff
path: root/.gitlab
diff options
context:
space:
mode:
authorHaelwenn <contact+git.pleroma.social@hacktivis.me>2023-05-17 15:49:54 +0000
committerHaelwenn <contact+git.pleroma.social@hacktivis.me>2023-05-17 15:49:54 +0000
commitb8b15cec9e18b434cf65aa6c496c7c8d215c4d73 (patch)
tree9d3a216148665480b9c783745b0121c3f26bd1dd /.gitlab
parent143676f58c8a5c0805af73ba7a86bdcc4dc85b13 (diff)
parent6a3fd8e01404f7fc4415626300d81c65c045a7d6 (diff)
downloadpleroma-b8b15cec9e18b434cf65aa6c496c7c8d215c4d73.tar.gz
pleroma-b8b15cec9e18b434cf65aa6c496c7c8d215c4d73.zip
Merge branch 'tusooa/changelog-improve' into 'develop'
Use git diff to search for changelog entry See merge request pleroma/pleroma!3875
Diffstat (limited to '.gitlab')
-rw-r--r--.gitlab/merge_request_templates/Default.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/.gitlab/merge_request_templates/Default.md b/.gitlab/merge_request_templates/Default.md
new file mode 100644
index 000000000..fdf219f99
--- /dev/null
+++ b/.gitlab/merge_request_templates/Default.md
@@ -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`, `remove`, `fix`, `security` or `skip`. `skip` is only used if there is no user-visible change in the MR (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 an MR 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 MRs. 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).