Update topic templates

No LLM usage for code.
Discourage LLM usage for bug reports.
Trim down other instructions.

Author: tarsius

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,9 +4,32 @@ name: 🪳 Report a bug
 about: Report a defect. Do not use this for support requests and feature suggestions.
 ---
 
-<!-- We now only use the issue tracker for issues, i.e., bugs and features
-that we have decided to work on.  If you are asking for help, want to make
-a suggestion, or are unsure, then please open a discussion. -->
+Please use your own words.
+Please use your own brain.
 
-<!-- Please use your own words.  If you really must use a LLM, at least
-disclose that upfront.-->
+Avoid stochastic parrots!
+Avoid LLMs!
+
+▄████▄ ▄▄ ▄▄  ▄▄▄  ▄▄ ▄▄▄▄     ▄████  ▄▄▄▄▄ ▄▄  ▄▄ ▄████▄ ██
+██▄▄██ ██▄██ ██▀██ ██ ██▀██   ██  ▄▄▄ ██▄▄  ███▄██ ██▄▄██ ██
+██  ██  ▀█▀  ▀███▀ ██ ████▀    ▀███▀  ██▄▄▄ ██ ▀██ ██  ██ ██
+
+If you have already used an LLM to investigate an issue, don't post a generated wall of text.  A human has to read and verify all that.  Please do that work yourself and then use your own words to describe the relevant findings.
+
+Disclose the LLM usage upfront.
+
+======================================================================
+
+We use this issue tracker only for issues suspected to be caused by bugs.  If you need help or want to make a suggestion, please instead open a discussion.
+
+======================================================================
+
+Before reporting a defect, please try to reproduce the issue using the latest releases or snapshots of all involved packages.  Mention the versions you used.
+
+Likewise try to reproduce it using an Emacs instance, in which only this package and its dependencies have been loaded.  Other packages or your configuration should not be loaded.
+
+======================================================================
+
+Explain (1) what behavior you expected, (2) what behavior you observed, (3) and how we can reproduce the issue.
+
+Do "M-x magit-version", trigger the issue again, and post the backtrace.

.github/PULL_REQUEST_TEMPLATE

@@ -1,29 +1,20 @@
-=================================================================
-Please use your own words
-=================================================================
+Please use your own words.
+Please use your own brain.
 
-Please use your own words, in this summary, commit messages and code.  If you really must use a LLM, at least disclose that upfront.  Code written by a LLM is not accepted.
+No stochastic parrots!
+No LLMs!
 
-=================================================================
-Use a dedicated feature branch
-=================================================================
+ ▐ ▄            ▄▄▄· ▪
+•█▌▐█▪         ▐█ ▀█ ██
+▐█▐▐▌ ▄█▀▄     ▄█▀▀█ ▐█
+██▐█▌▐█▌.▐▌    ▐█ ▪▐▌▐█▌
+▀▀ █▪ ▀█▄▀▪     ▀  ▀ ▀▀▀
 
-Please use a dedicated feature branch for your feature request, instead of asking us to merge "your-fork/master" into "origin/master".  The use of dedicated branches makes it much more convenient to deal with pull-requests, especially when using Magit to do so.
-
-If you were about to open a pull-request asking us to merge your version of "master", then see [1] for instructions on how to quickly fix that and some information on why we ask you to do so.
-
-Additionally we ask you to allow us to push to the branch you want us to merge.  We might want to push additional commits and/or make minor changes.  Please make sure the box next to "Allow edits from maintainers" is checked before creating the pull-request.
-
-  [1]: https://github.com/magit/magit/wiki/Dedicated-pull-request-branches
-
-=================================================================
-What you should write here
-=================================================================
+Before making significant changes or additions, consider first opening an "idea" discussion.  For trivial changes, skip that step.
 
 Please summarize the changes made in the commits.  Explain why you are making these changes, not just what changes you are making.  This also applies to the commit messages.
 
-=================================================================
-How to update the manual
-=================================================================
-
-Edit only "borg.org".  To update "borg.texi" run "make texi".
+Please also
+- use a dedicated feature branch instead of working on "main"
+- use Emacs even for miniscule changes, not the web interface
+- edit "docs/*.org", not "docs/*.texi", then run "make texi"