diff options
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 26f15156..28a853a9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,18 +34,6 @@ Source code is extensively commented for that purpose, raylib primary learning m > learn by reading code and examples - -### Using raylib develop branch - -raylib [master branch](https://github.com/raysan5/raylib) contains the latest raylib release but all -the future work is always done on [develop branch](https://github.com/raysan5/raylib/tree/develop), -it's far ahead of master and I try to keep it always stable with latest library changes. - -Please, if issuing a bug or sending a pull-request, verify that you're using develop branch. - -Note that while using develop branch predefined Notepad++ building scripts could not work, in that case, -use provided [Makefile](https://github.com/raysan5/raylib/blob/develop/src/Makefile) or [CMake](https://github.com/raysan5/raylib/blob/develop/src/CMakeLists.txt) building systems. - For detailed information on building raylib and examples, please check [raylib Wiki](https://github.com/raysan5/raylib/wiki). ### Opening new Issues @@ -62,8 +50,6 @@ To open new issue for raylib (bug, enhancement, discussion...), just try to foll ### Sending a Pull-Request -To send a pull-request, first of all, make sure you're sending it to [develop branch](https://github.com/raysan5/raylib/tree/develop). Here are some other rules: - - Make sure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable. - Don't send big pull-requests (lots of changelists), they are difficult to review. It's better to send small pull-request, one at a time. - Verify that changes don't break the build (at least on Windows platform). As many platforms where you can test it, the better, but don't worry |