Piotr Galar

Nice, thanks for adding this information to the issue. The comment command set you proposed seems very reasonable as well. In the meantime, I found one case which might be...

#### Brain dump I think this could work something like this. Let's say I want the bot to do something. I would create a GitHub issue in the `github-mgmt` repository....

Here's a run with full diff - https://github.com/libp2p/go-libp2p/actions/runs/9974916892/job/27563846282 I'll make sure we have the diff available on failures in the next release of uci.

> Instead of this reporter knowing about it, we should provide a generic solution to customize the how the details of an error are displayed. > > I imagine something...

> > Unfortunately, I discovered that when the node test runner executes tests in process isolation mode (the default), unsurprisingly, we don't have access to class methods :( > >...

No rush, take your time :) And if there's anything that needs some more clarification, let me know

> This is really interesting. I'm still processing and reading through some parts of it, as this makes me read more docs than a usual PR, but there are some...

I'm closing this PR as we agreed to: 1. Split it into smaller chunks to make it easier to review & merge. 2. Target the `v-next` branch instead.

I put together a design doc for this as per the description - https://www.notion.so/nomicfoundation/Hardhat-Dependency-Tracking-4da1bbd17a7443b7a2ab9f9da1931903?pvs=4 The solution I proposed is already implemented at https://github.com/NomicFoundation/hardhat/pull/5653 because it came together as I explored...

@MarcoPolo It looks like that's `go fix` that's doing it.