Continuing the discussion from Any mutt hackers on here?:
Okay, here is the deal: I want to quickly process my inbox, by creating todos for myself in GitLab.
I have issue creation by email working in GitLab, but there are two things that aren’t working as I want.
First, when an issue is created, it is authored by me, as expected, but nothing else happens. I have a private repo set up, but I also want the issues assigned to me, and to be marked as a todo in GitLab. I can fix that by including a slash command in the message, specifically
The second issue I have is that mutt is forwarding in a way that I don’t understand, because I don’t deal with message headers very often. I thought maybe forwarding was broken with GitLab, but I tested with a different email client (Geary) and the forward worked as expected. I will show ya what I mean.
I asked @tim to send me an email, from which to create an issue.
If I forward from mutt, the issue is created like so:
That isn’t great. Here is the forward from Geary:
That is more of what I am looking for. One last thing, in my troubleshooting I learned about “bouncing” a message in mutt. Even though the message ought to be accepted as it is verified by the secret email address that contains a personal token, it still doesn’t accept the message, and instead replies with an error message to the original sender, like so (thanks @tim!):
What I need to know
My ideal scenario is that I tag one or more messages in mutt and then have them become todo issues assigned to me. As I am not adding additional content, it seems like a message bounce is the best practice, except I don’t know of another way to assign it to me sans a slash command.
Therefore, what I need to figure out is modifying the forwarded message so it not only includes the slash command, but also formats the message in a way that is parsed by GitLab.
I fairly certain I can create a macro to add the slash command and bind it to a key, but I can’t quite figure out how to format the forward template in mutt. If I can figure that out, maybe I can get it working the way I want. I included all the moving parts in the case an alternative exists that eludes me.