AI-assisted PRs and CONTRIBUTING.md

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

Small suggestions

  1. AI-assisted pull requests are welcome. The contributor is responsible for the change and must have read, run and understood all of it.
  2. 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.
  3. 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.
  4. A human reads the pull request before asking for review. Comments and replies are written by the person, not by an unattended agent.
  5. Take extra care with changes to restore, prune, check and the repository format.

If this is not useful, no problem. Thanks for restic.

Thanks for your thoughts and how well you structured them :slight_smile: I can let you know that there is ongoing work in regards to formulating guidance regarding AI in contributions.

1 Like