Hello all,

This is a feature suggestion that has bounced into my head. It could be 
beneficial for novices to patch-based development browsing ticket 
trackers to have a handy method for queuing and sending their 
contributions. The method I took is to provide a template for 
git-send-email commands in the tickets themselves. An example of such 
can be seen at [0]. The idea I have is for this to be optionally enabled 
in the TODO service, taking care to populate the commit messages with 
the snippet ID and title, as well as linking to the preferred 
development mailing list.

This idea may have no merit, but I wanted to make sure it was at least 
put out there.

Happy hacking,

Brett Gilio


[0]: https://todo.sr.ht/~brettgilio/snippet/1

hi

On Sun Jul 17, 2022 at 5:10 PM PDT, Brett Gilio wrote:
> The method I took is to provide a template for git-send-email commands
> in the tickets themselves. An example of such can be seen at [0]. The
> idea I have is for this to be optionally enabled in the TODO service,
> taking care to populate the commit messages with the snippet ID and
> title, as well as linking to the preferred development mailing list.
> ...snip...
> [0]: https://todo.sr.ht/~brettgilio/snippet/1

as an aside to provide more ways this can be expanded on, there are some
projects that request their contributors apply git trailers to their
commits with relevant information, one of which what issue / todo the
commit "fixes".

an example commit:

    some commit message
    
    Fixes: https://todo.sr.ht/~sourcehutuser/project/todo_number


and then, the linked todo will automatically be marked as fixed on the
tracker if the patch is merged upstream.

Hello Akspecs

On 7/17/2022 7:26 PM, akspecs wrote:
> and then, the linked todo will automatically be marked as fixed on the
> tracker if the patch is merged upstream.


Is that functionality already implemented, or is that something which is 
being proposed? If it is already implemented, then it would be 
imperative that data be retained in trackers as pre-populated information.

Brett Gilio

> Is that functionality already implemented, or is that something which
> is being proposed?

Already implemented – see here:

    https://man.sr.ht/git.sr.ht/#referencing-tickets-in-git-commit-messages

-- 
/Liele Zerau (they/them)
PGP-key: 32AE B0C8 E86B 5971 509B 67B3 465A 9567 984C 81F3

Hello Liele

On 7/18/2022 8:57 AM, Liele Zerau wrote:
>> Is that functionality already implemented, or is that something which
>> is being proposed?
> Already implemented – see here:
>
>      https://man.sr.ht/git.sr.ht/#referencing-tickets-in-git-commit-messages

Thank you for that information. Good to know. Drew is not fond of the 
idea I proposed, but I learned a good bit.

Brett