Re: [PATCH] [pre-commit] Add shellcheck

On 6/22/26 10:58 AM, Tom de Vries wrote:
>> Could you maybe submit a .pre-commit-hooks.yaml to that project?  And
>> then we can point to a specific tag/hash of that repo.  If we don't hear
>> anything from them after a few weeks then we could consider your fork,
>> but if we can have the hooks upstream from the start it's less
>> maintenance.
>>
> 
> I've done that, and submitted fixes for two problems.
> 
> If that doesn't work out, perhaps some setup on our local sourceware 
> forge owned by the gdb project rather than my personal github account 
> would be better.  Not sure how to get that setup though, I haven't used 
> it yet.

Hi Simon,

coming back to this, it's been a month, and there's no reaction.  So it 
could well be that we're looking at an unmaintained project.

I thought about whether I would want to maintain a clone, but came 
across this cautionary tale [1]. So, given that the project published 
the code but not the prompts, trying to maintain it could be a time 
sink, so I decided against it.

So I'm dropping this.  I'm going to propose something simpler.

Thanks,
- Tom

[1] 
https://developers.redhat.com/articles/2026/02/17/uncomfortable-truth-about-vibe-coding#where_it_falls_apart