docs(agents): define contribution and review requirements

Keep commit history self-contained and issue links visible on the PR.
Distinguish commit-reference trailers from issue-closing references,
and reserve closing keywords for complete fixes.

Include review bodies, conversation and commit comments alongside inline
threads without imposing the same review depth on every change. Verify
feedback against current code before acting on it.

Validation: markdownlint passes with MD013 excluded, and MD041 excluded
for the PR template, whose existing first heading is level two.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
This commit is contained in:
Aleksei Sviridkin committed 2026-11-12 16:53:23 +03:00
1 parent 1e7ba63c57
commit 7475c5af5d
2 files changed
+47 -66

No files matched your search

+1
View File
@@ -13,6 +13,7 @@
## What this PR does
<!-- Link the issues this PR addresses. For a complete fix targeting the default branch, use Closes #N (Closes owner/repository#N for another repository). Otherwise use a non-closing reference; release-branch PRs need manual issue linking and closure when appropriate. -->
### Screenshots