From a15f1a52c79e10ad863f5e3409c890501577d384 Mon Sep 17 00:00:00 2001 From: Rangi <35663410+Rangi42@users.noreply.github.com> Date: Wed, 25 Oct 2023 18:44:01 -0400 Subject: [PATCH] contributing: update repository links (rednex -> gbdev org) (#1177) --- CONTRIBUTING.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 605660d6b..6b4992fce 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -12,14 +12,14 @@ Bug reports are essential to improve RGBDS and they are always welcome. If you want to report a bug: 1. Make sure that there isn't a similar issue already reported - `here `__. + `here `__. 2. Figure out a way of reproducing it reliably. 3. If there is a piece of code that triggers the bug, try to reduce it to the smallest file you can. -4. Create a new `issue `__. +4. Create a new `issue `__. Of course, it may not always be possible to give an accurate bug report, but it always helps to fix it. @@ -30,7 +30,7 @@ Requesting new features If you come up with a good idea that could be implemented, you can propose it to be done. -1. Create a new `issue `__. +1. Create a new `issue `__. 2. Try to be as accurate as possible. Describe what you need and why you need it, maybe with examples. @@ -49,7 +49,7 @@ if your change is going to be small (and likely to be accepted as-is) or big (and will have to go through some rework). Big changes will most likely require some discussion, so open an -`issue `__ and explain what you want to +`issue `__ and explain what you want to do and how you intend to do it. If you already have a prototype, it's always a good idea to show it. Tests help, too.