summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordelvh <dev.lh@web.de>2024-02-26 23:04:44 +0100
committerGitHub <noreply@github.com>2024-02-26 17:04:44 -0500
commit4f70ebb68494b23c5bce93efbe4c5f80b3aaf444 (patch)
treeddb6dbcd9df352d34c5040ee88293f18dbf78ee0
parent324626a11c041208b003ee64e33000b223994662 (diff)
downloadgitea-4f70ebb68494b23c5bce93efbe4c5f80b3aaf444.tar.gz
gitea-4f70ebb68494b23c5bce93efbe4c5f80b3aaf444.zip
Document our issue locking policy (#29433)
-rw-r--r--CONTRIBUTING.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f9b9a421a3..dc90c6905b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -8,6 +8,7 @@
- [How to report issues](#how-to-report-issues)
- [Types of issues](#types-of-issues)
- [Discuss your design before the implementation](#discuss-your-design-before-the-implementation)
+ - [Issue locking](#issue-locking)
- [Building Gitea](#building-gitea)
- [Dependencies](#dependencies)
- [Backend](#backend)
@@ -103,6 +104,13 @@ the goals for the project and tools.
Pull requests should not be the place for architecture discussions.
+### Issue locking
+
+Commenting on closed or merged issues/PRs is strongly discouraged.
+Such comments will likely be overlooked as some maintainers may not view notifications on closed issues, thinking that the item is resolved.
+As such, commenting on closed/merged issues/PRs may be disabled prior to the scheduled auto-locking if a discussion starts or if unrelated comments are posted.
+If further discussion is needed, we encourage you to open a new issue instead and we recommend linking to the issue/PR in question for context.
+
## Building Gitea
See the [development setup instructions](https://docs.gitea.com/development/hacking-on-gitea).