Thanks Pedro!. I think you've solved it for me. Much appreciated.

> After you reviewed a patch that looks good to go, you should pipe it
> into git am. If you use mutt, you can just use the pipe command (| by
> default) and type git am -, same goes to aerc (I don't use it so I don't
> know what command it is, but it is surely documented).

Thank you so much!. That I can pipe a message as std-in to any shell
command was the missing secret sauce. Mutt seems powerful, but
there is so much to learn :). Until you mentioned that I though people
had all setup there own scripts to automate and filter mutt somehow.

> > If anyone knows of a good blog or workflow explaining this it would be
> > much appreciated.

Hi All,

I've always loved the concept of collaborating more using email, and
absolutely love https://git-send-email.io/. This seems like a great
workflow for sending patches.

For the other half as a maintainer, I have gotten a bit lost.
I would be able to review code in my email client and respond, but I'm
not sure how to then get the commits or patches out of git and then
apply them to my repository to 'merge' in.

I haven't yet had any patches come to my sourcehut repos, but I'd want
to be prepared so I am able to merge anything in that I am happy with.
This would also help me influence some peers to get on board the

Hi All,

Apologies if I mess up the mailing list, my first time using mutt and
discussing things this way.

Just wondering if there is anyone who has built anything similar to the
'automatic merge' when approved and passed CI like some other services
have. I figure the analogue here would be something watching the mailing
list for 'approved' email signed by a valid GPG key, then the bot would
merge it back to main.

Currently this would probably need to be automated outside of sourcehut.
As you would need to maintain some secret to update the master.