2026-04-03 19:05 UTC
@edwintorok@discuss.systems this proposal deliberately doesn’t depend on VCS info: it’s a marker in the code itself that’s easy to keep across rebase etc and also for the human to edit
Replies (1)
-
@edwintorok@discuss.systems 2026-04-03 19:17
@avsm@amok.recoil.org perhaps a `lint` tool could check the consistency between information in the repository, and information in the VCS. They are both useful for different reasons (e.g. disclosure in the commit itself can help reviewers, and may be required by some projects; whereas the info in the repo is a good way to tell at a glance how AI is used in a project, or in places where VCS is unavailable, like an `opam` release).