Thank you to everyone who develops and maintains restic. I use it for backups that are very important to me.
Disclosure: I am a restic user, not a Go developer. I used Claude to help me read recent commits and open pull requests.
Question
Would a few lines about AI-assisted pull requests in CONTRIBUTING.md be useful? I’m not asking for a ban, a general debate about AI or raising criticisms about any contributor.
Why I ask
- More pull requests now say they were written with AI tools.
- In restic is tainted by “AI” slop · Issue #21898 · restic/restic · GitHub Michael wrote that an acceptable-use policy might be needed someday, and that AI use so far looks responsible.
- In `RESTIC_REST_PASSWORD` ignored with `username@domain` URL · Issue #22035 · restic/restic · GitHub he wrote that unsupervised AI agent activity is disrespectful to maintainers. A written rule would tell new contributors this before a problem happens.
- Restic stores data that people cannot recreate, so errors in restore, prune or check are costly.
Small suggestions
- AI-assisted pull requests are welcome. The contributor is responsible for the change and must have read, run and understood all of it.
- The contributor states which tool was used, for example with an
Assisted-by:commit trailer. Commit bba1b6808 (prune error handling) is a good example of a clear description: motivation, approach, validation and what was not reproduced. - Add a question to the pull request template: “Which backend or filesystem did you test on?” Unit tests cannot show how real NFS or REST servers behave.
- A human reads the pull request before asking for review. Comments and replies are written by the person, not by an unattended agent.
- Take extra care with changes to restore, prune, check and the repository format.
If this is not useful, no problem. Thanks for restic.