From fc3ed0c0240ff823fd96a5bc38746bf451c3b3c5 Mon Sep 17 00:00:00 2001 From: Andreas Dutzler Date: Sun, 22 Sep 2024 00:46:42 +0200 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dc1e5d7e..b841903f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -69,9 +69,9 @@ A good bug report shouldn't leave others needing to chase you up for more inform > You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to . -We use GitHub issues to track bugs and errors. If you run into an issue with the project: +We use [GitHub issues](https://github.com/adtzlr/felupe/issues) to track bugs and errors. If you run into an issue with the project: -- Open an [Issue](https://github.com/adtzlr/felupe/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.) +- Open an [Issue](https://github.com/adtzlr/felupe/issues/new/choose). - Explain the behavior you would expect and the actual behavior. - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case. - Provide the information you collected in the previous section.