| 1 |
On Tue, Jan 25, 2022 at 9:00 AM Michael Orlitzky <mjo@g.o> wrote: |
| 2 |
> |
| 3 |
> Can I request that Bug: and Closes: tags in our commits automatically |
| 4 |
> CC the committer on the bug that is modified? |
| 5 |
> |
| 6 |
> Use case: I often fix (sci-*) bugs that I'm not CCed on, and a user |
| 7 |
> will leave a comment like "it still crashes on x86" that I never see. |
| 8 |
> Of course, I could manually CC myself on every bug. But that will send |
| 9 |
> everyone an extra email, and is forgettable. Plus, avoiding the manual |
| 10 |
> step is kind of the point of the automation, right? |
| 11 |
|
| 12 |
Just to clarify here: |
| 13 |
For your own commits (e.g. fixing a package you own) you are already |
| 14 |
typically on the bug..right? |
| 15 |
I assume the major use case here is proxying commits for others (where |
| 16 |
they are on the bug, but you are not, either directly, or via an |
| 17 |
alias?) |
| 18 |
|
| 19 |
> |
| 20 |
> One potential downside is that the commit author could wind up CCed |
| 21 |
> twice via an alias, but that could be solved with a sufficiently clever |
| 22 |
> implementation. Or disregarded if it's not too much of a problem in |
| 23 |
> practice; the bugs will usually be closed, after all. |
| 24 |
|
| 25 |
The hooks are all public: |
| 26 |
|
| 27 |
https://gitweb.gentoo.org/infra/githooks.git/tree/local/postrecv-bugs |
| 28 |
|
| 29 |
Submit a patch and we can update the hook. |
| 30 |
|
| 31 |
-A |
| 32 |
|
| 33 |
> |
| 34 |
> |
| 35 |
> |
Archives