From 97ae17cab32df8e166d258ef8a733724cb2d1f54 Mon Sep 17 00:00:00 2001 From: Deluan Date: Sun, 8 Nov 2026 18:01:18 -0500 Subject: [PATCH] docs: ask before working on an issue someone offered to fix When an issue author or another contributor offers to submit a fix, others should ask in the issue before starting their own PR. This avoids duplicate work and gives the person who did the investigation the first chance to contribute the fix. Signed-off-by: Deluan --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4b1501aeb..2f8381ce5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -50,7 +50,7 @@ The maintainer must be able to understand and maintain the result without depend ## Submitting and review -- Check existing [open and closed PRs](https://github.com/navidrome/navidrome/pulls?q=is%3Apr) to avoid duplicate work. +- Check existing [open and closed PRs](https://github.com/navidrome/navidrome/pulls?q=is%3Apr) to avoid duplicate work. If the issue author or another contributor has offered to submit a fix, ask in the issue before you start. - Use the [development environment instructions](https://www.navidrome.org/docs/developers/dev-environment/). Work on a branch in your fork. - Complete the [PR template](.github/pull_request_template.md) with the scope agreement or why agreement is not needed, verification evidence, and maintenance implications. Keep each PR focused. - Follow the [commit conventions and DCO requirements](#commit-conventions-and-dco) below.