gbdev/rgbds
1
0
Fork 0
mirror of https://github.com/gbdev/rgbds.git synced 2025-11-20 10:12:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

contributing: update repository links (rednex -> gbdev org) (#1177)

Browse Source
This commit is contained in:
Rangi
2023-10-25 18:44:01 -04:00
committed by GitHub
parent 944c5f0cd0
commit a15f1a52c7
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.rst
View File

@@ -12,14 +12,14 @@ Bug reports are essential to improve RGBDS and they are always welcome. If you
want to report a bug: want to report a bug:
1. Make sure that there isn't a similar issue already reported 1. Make sure that there isn't a similar issue already reported
`here <https://github.com/rednex/rgbds/issues>`__. `here <https://github.com/gbdev/rgbds/issues>`__.
2. Figure out a way of reproducing it reliably. 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 3. If there is a piece of code that triggers the bug, try to reduce it to the
smallest file you can. smallest file you can.
4. Create a new `issue <https://github.com/rednex/rgbds/issues>`__. 4. Create a new `issue <https://github.com/gbdev/rgbds/issues>`__.
Of course, it may not always be possible to give an accurate bug report, but it Of course, it may not always be possible to give an accurate bug report, but it
always helps to fix 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 If you come up with a good idea that could be implemented, you can propose it to
be done. be done.
1. Create a new `issue <https://github.com/rednex/rgbds/issues>`__. 1. Create a new `issue <https://github.com/gbdev/rgbds/issues>`__.
2. Try to be as accurate as possible. Describe what you need and why you need 2. Try to be as accurate as possible. Describe what you need and why you need
it, maybe with examples. 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). (and will have to go through some rework).
Big changes will most likely require some discussion, so open an Big changes will most likely require some discussion, so open an
`issue <https://github.com/rednex/rgbds/issues>`__ and explain what you want to `issue <https://github.com/gbdev/rgbds/issues>`__ and explain what you want to
do and how you intend to do it. If you already have a prototype, it's always a 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. good idea to show it. Tests help, too.