>jeu. 12 nov. 2026 at 11:16, Andreas Enge <[email protected]> wrote:

> On Sat, Nov 07, 2026 at 09:44:57PM +0100, Ludovic Courtès wrote:
>> I have this in ~/.gitconfig:
>> --8<---------------cut here---------------start------------->8---
>> [alias]
>>      merge-pull-request="!m() { set -o pipefail; set -e; for id in $(git 
>> cherry HEAD
>> pulls/pr/$1 | cut -c2-); do git cherry-pick --signoff $id; done; git commit 
>> --amend
>> --no-edit --trailer 'Merges: #'$1; }; m"
>> --8<---------------cut here---------------end--------------->8---
>> Thus, when I do ‘git merge-pull-request 123’, it automatically adds
>> “Merges: #123” as a trailer on the last commit.
>> I think we should agree on committers taking care of adding the trailer
>> via a tool along these lines.
>
> I have just tried it out, and it works well. Thanks!
>
> Concerning the format, I am also seeing this:
>    Merges: guix/guix!123
> and for issues we use
>    Fixes: guix/guix#123
>
> Maybe we should standardise towards
>    Merges: guix/guix#123

This is something which comes from forgejo/codeberg itself, see [0],[1] for
example, under "Reference".

I remember a place in the forgejo doc where they explain there is a
difference between # (for issues) and ! (for pull requests).

C.

[0] https://codeberg.org/guix/guix/pulls/12478
[1] https://codeberg.org/guix/guix/issues/12479

Reply via email to