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

Remove develop branch from contributing guide

Browse Source 
This branch was meant to contain changes that were considered too risky
to be in master. However, there is not enough activity in the repository
to justify its presence. Both branches are always pointing at the same
commit.

Signed-off-by: Antonio Niño Díaz <antonio_nd@outlook.com>
This commit is contained in:
Antonio Niño Díaz
2019-05-05 23:38:26 +01:00
parent 6ff9435e0a
commit fa37922ca7
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

@@ -65,9 +65,9 @@ copyright and the reference to the MIT License.
1. Fork this repository. 1. Fork this repository.
2. Checkout the ``develop`` branch. 2. Checkout the ``master`` branch.
3. Create a new branch to work on. You could still work on ``develop``, but it's 3. Create a new branch to work on. You could still work on ``master``, but it's
easier that way. easier that way.
4. Compile your changes with ``make develop`` instead of just ``make``. This 4. Compile your changes with ``make develop`` instead of just ``make``. This
@@ -90,7 +90,7 @@ copyright and the reference to the MIT License.
long as you specify it when executing the command: long as you specify it when executing the command:
``CHECKPATCH=../path/to/folder make checkpatch``. ``CHECKPATCH=../path/to/folder make checkpatch``.
8. Create a pull request against the branch ``develop``. 8. Create a pull request against the branch ``master``.
9. Be prepared to get some comments about your code and to modify it. Tip: Use 9. Be prepared to get some comments about your code and to modify it. Tip: Use
``git rebase -i origin/develop`` to modify chains of commits. ``git rebase -i origin/master`` to modify chains of commits.