diff options
| author | Zaven Muradyan <voithos@google.com> | 2018-10-13 22:59:52 -0700 |
|---|---|---|
| committer | Zaven Muradyan <voithos@google.com> | 2018-10-13 22:59:52 -0700 |
| commit | 172694ac4ca5aac60b82a354cfb491bc545c8914 (patch) | |
| tree | 52562054a0e01623c5f6e48dc9b83cc7486667b4 /CONTRIBUTING.md | |
| parent | 451e5fd0511bc2c17a66fc73a0de9a5169109517 (diff) | |
| download | redot-engine-172694ac4ca5aac60b82a354cfb491bc545c8914.tar.gz | |
Add useful links for contributors to CONTRIBUTING and README docs.
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 68ec20a525..2ea2ed6bba 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -70,11 +70,15 @@ Similar rules can be applied when contributing bug fixes - it's always best to discuss the implementation in the bug report first if you are not 100% about what would be the best fix. +In addition to the following tips, also take a look at the +[Engine development guide](http://docs.godotengine.org/en/latest/development/cpp/) +for an introduction to developing on Godot. + #### Be nice to the git history -Try to make simple PRs with that handle one specific topic. Just like for -reporting issues, it's better to open 3 different PRs that each address a -different issue than one big PR with three commits. +Try to make simple PRs that handle one specific topic. Just like for reporting +issues, it's better to open 3 different PRs that each address a different issue +than one big PR with three commits. When updating your fork with upstream changes, please use ``git pull --rebase`` to avoid creating "merge commits". Those commits unnecessarily pollute the git |