Re: [PATCH 0/9] ci: make Git's GitHub workflow output much more helpful
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 20, 2022, 02:44 UTC
- Message-ID
- <xmqqtucuw93i.fsf@gitster.g>
- In-Reply-To
- <nycvar.QRO.7.76.6.2202200043590.26495@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 6 quoted lines
> I notice that you did not take this into `seen` yet. I find that a little > sad because it would potentially have helped others to figure out the > failure in the latest `seen`: > https://github.com/git/git/runs/5255378056?check_suite_focus=true#step:5:162 > > Essentially, a recent patch introduces hard-coded SHA-1 hashes in t3007.3.
I saw the thread, I saw a few patches were commented on, and a few were left unanswered, but one was replied by the original submitter with a "Good catch!", making me expect the topic to be discussed or rerolled to become ready relatively soon.
But nothing happened, so I even forgot to take a look myself by picking it up in 'seen'. It does sound sad that the topic was left hanging there for 3 weeks or so in that state without any reroll or response.