Editing Hacking:Making pull requests

Jump to: navigation, search

Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.

The system administrator who locked it offered this explanation: Upgrading to MediaWiki 1.31

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 19: 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.
 
* 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.
 
* Compiler should successfully build each commit you made.
* Make all your commits in '''develop/release''' branch. This mean all your changes in your local repository will be only in '''develop/release''' branch.
+
* Make all your commits in '''feature''' branch. This mean all your changes in your local repository will be only in '''feature''' branch.
* Don't forget each day sync your repository with ours and merge new code in '''develop/release''' branch -> to your '''develop/release''' branch. Fix all merge conflicts.
+
* Don't forget each day sync your repository with ours and merge new code in '''develop/release''' branch -> to your '''feature''' branch. Fix all merge conflicts.
* You can push your '''develop/release''' branch to bitbucket. This will help us watch your progress and leave comments. We recommend don't hide your code until the end.  
+
* You can push your '''feature''' 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 '''develop/release''' branch to the upstream repository.
+
* When you will decide that all were done create a pull request. In settings set to push your '''feature''' branch to the upstream repository.
* If we ask you to fix some issues related to your changes continue commit them to the '''develop/release''' branch and push them to bitbucket. It will automatically update your pull request.
+
* If we ask you to fix some issues related to your changes continue commit them to the '''feature''' branch and push them to bitbucket. It will automatically update your pull request.
  
 
== General recommendations ==
 
== General recommendations ==

Please note that all contributions to Seamly2D are considered to be released under the Creative Commons Attribution Share Alike (see Seamly2D:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)