logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma git clone https://hacktivis.me/git/pleroma.git
commit: 1036acb6ae33d2bdc2afa4abfe8f9e9f8864137a
parent 633a76b5b3b9f8edfa7f342e00a992016e3284c0
Author: tusooa <tusooa@kazv.moe>
Date:   Tue,  6 Dec 2022 20:41:22 +0000

Merge branch 'release-template' into 'develop'

Add Gitlab Releaseā„¢ into Release MR template

See merge request pleroma/pleroma!3797

Diffstat:

M.gitlab/merge_request_templates/Release.md10++++++----
1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/.gitlab/merge_request_templates/Release.md b/.gitlab/merge_request_templates/Release.md @@ -1,6 +1,8 @@ ### Release checklist -* [ ] Bump version in `mix.exs` -* [ ] Compile a changelog -* [ ] Create an MR with an announcement to pleroma.social -* [ ] Tag the release +* [ ] Bump version in `mix.exs` +* [ ] Compile a changelog +* [ ] Create an MR with an announcement to pleroma.social +#### post-merge +* [ ] Tag the release on the merge commit +* [ ] Make the tag into a Gitlab Releaseā„¢ * [ ] Merge `stable` into `develop` (in case the fixes are already in develop, use `git merge -s ours --no-commit` and manually merge the changelogs)