At $DAYJOB, we have an org for the project and tag images as ci-$distro-$version-$arch-YYYYMMDD[.N] (or drop-$arch and use manifest images with multiple arches available under a single tag).…

Does Forgejo have a container registry?

Does this test end up playing with the state of the Git repo? That's going to conflict with any other test also wanting to do that. We have a crate that [sets of a "workarea"](https://gitlab.kitwar…

I think this is fine, thanks.

I see it as a way to tell mergiraf the language to use. If you also use linguist-language, that is also looked up as a fallback so that mergiraf.language isn't needed.

No idea what happened; the original comment is gone :/ . I blame early morning intersecting Codeberg unfamiliarity.

This paragraph can be removed if the list is sorted and introduced with …for this purpose, in order:

Minor request. Looks good other than that!

That's probably fine for now; I don't expect any #cfg blocks in the project to suddenly start showing up (CMake definitely has files that don't get compiled on each platform…and doing things…

Clippy enforcement in CI is great. I am suggesting tools for easing fixing it for developers.

Recording a Vim macro :) . Finds the next instance, deletes to the (, then deletes the surrounding (.

There's no general way to know that. I suppose for a token or path thereof, you can, but dbg!(some_call()); shouldn't be taken away completely. At that point though, your diff is something like:

Is --tests included in --all-features or is CI blind to clippy lints in test code here?

The main benefit, IMO, is that ast-grep is blind to #[cfg] bits, so it also always gets the dbg! calls from your tests too. I imagine the suggested command line also fails to forward…

I wrote an ast-grep fixit to do this automatically for CMake here. Shouldn't be too hard to…