pr template: ask contributors to review and copy-edit AI contributions 82944918 parent e1365d7f

The goal is to nudge contributors towards taking on the burden of understanding and editing any AI-generated work they are trying to get reviewed. AFAICT, jj is currently less overwhelmed with low-quality AI contributions than to some other projects, but it started to happen occasionally. For now, this is partly an experiment as opposed to a fixed rule. Will the people who most need this guidance read it and benefit from it? Hopefully, they'll try to or will ask questions. I considered also adding a clarification to the second point, suggesting something like "If in doubt, delete all the AI-generated text and rewrite it in your own words", but that point was already getting long. We could add something like that later. See https://github.com/jj-vcs/jj/pull/8897#discussion_r2815120348 for some reasons I didn't want to require disclosing whether people used AI tools while preparing the PR.

authored by Ilya Grigoriev committed by Ilya Grigoriev

1
/target/
2
/rendered-docs
3
.direnv
4
.envrc
5
# Generated by nix build, nix-build
6
result
7
# Generated by the insta crate
8
*.pending-snap
9
*.snap*
10
!cli/tests/cli-reference@.md.snap
11
# Per user insta settings.
12
# See https://insta.rs/docs/settings/#tool-config-file for details.
13
.config/insta.yaml
14
# Per user mise config
15
mise.local.toml
16
17
# mkdocs
18
/.venv
19
/.python-version
20
21
# Editor specific ignores
22
.idea
23
.vscode
24
.zed
25
26
# Generated by setting `JJ_TRACE` environment variable.
27
jj-trace-*.json
28
29
# To make working on buck2 easier (#1997, #4413)
30
/buck-out/
31