Hacking:Making pull requests: Difference between revisions

Line 19:
* Each commit should be small as possible and contain one logical step of developing a feature. This will help us better understand your code. Sometimes we see changes per each commit separately.
* Compiler should successfully build each commit you made.
* Make all your commits in '''featuredevelop/release''' branch. This mean all your changes in your local repository will be only in '''featuredevelop/release''' branch.
* Don't forget each day sync your repository with ours and merge new code in '''develop/release''' branch -> to your '''featuredevelop/release''' branch. Fix all merge conflicts.
* You can push your '''featuredevelop/release''' branch to bitbucket. This will help us watch your progress and leave comments. We recommend don't hide your code until the end.
* When you will decide that all were done create a pull request. In settings set to push your '''featuredevelop/release''' branch to the upstream repository.
* If we ask you to fix some issues related to your changes continue commit them to the '''featuredevelop/release''' branch and push them to bitbucket. It will automatically update your pull request.
 
== General recommendations ==