← Krita/FeatureBranchesWorkflow You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. == Publishing Feature Branches Review Requests == <ol> <li>All your work on implementing new features should happen in separate branches, not in master.</li> <li>Branch name should have the following structure <tt><yourname>/<featurename></tt></li> <li>Merging of the branches to master is allowed during the 2-week merge window in the beginning of every 6-weeks release cycle</li> <li>Before merging the branch into master, you should make a review request for it. </li> <pre> # switch to your branch git checkout your/branch/name # make sure you have pushed your work to the repository git push # fetch the latest changes in origin/master git fetch # generate a diff relative to the remote version of master arc diff origin/master </pre> '''NOTE:''' Make sure you didn't merge master into your branch manually right before generating a diff! If you did, arcanist will overwrite your merging commit. If he did, reset your current head to the latest pushed commit <pre>git reset --hard origin/<your/branch/name></pre></li> <li>Your review request text should be formatted as if it is a real commit. When you land the patch with arcanist, this text will be used for an actual commit. Use the following structure: <pre> One line short description of the changes Long description of the changed that happened lately in your branch with mentioning all the cute features it has and all the nice people you had to talk to to get the complete understanding of it. BUG:<bugnumber-you-fixed> Fixes T<phabricator-task-id-that-is-fixed> Ref T<phabricator-task-id-that-is-related-but-not-fixed> ## Add next line if your commit has features that need to be added to the Krita Manual Auditors:#krita_manual,#krita_website_and_translations ## Add next line if your commit has features that need to be publised in social media/site/twitter Auditors:#krita_website_and_translations </pre></li> <li>Make sure you added a keyword to close the bug you have fixed</li> <li>Make sure you added a keyword to close or reference the Maniphest ticket you have been working on</li> <li>When you got the review and want to update your patch, do <pre> git push git fetch arc diff --update D<your-revision-id> origin/master </pre></li> <li>When you have green light for merging your branch into master, land it with the following command: <pre> git checkout your/branch/name arc land --merge --hold </pre></li> <li>Make sure you use ''--merge'' option to avoid squashed commit. Squashed commits break ''git blame'' functionality, so are highly NOT recommended.</li> <li>Use ''--hold'' option to not allow arcanist to push your changes. It will prepare the commit for you, so you will be able to check the message and probably edit it with ''git commit --amend''</li> <li>After you checked the commit message and tags, push your changes to the repository</li> </ol> == Reviewing someone else's review requests == <ol> <li>To review a patch issue the following commands: <pre> git checkout master git pull arc patch D<revision-id> </pre> </li> <li>To switch back and cleanup arcanist's branches use the following [https://phabricator.kde.org/F213382 script]. <pre> git checkout master clean_arcanist </pre></li> <li> To push someone else's patch: <pre> git checkout master git pull arc patch D<revision-id> arc land --merge --hold # Now you are in a detached state with the HEAD set to your merge commit. # Please check if the commit has a correct commit message and has all # the necessary tags. # Add credits for the commit author git commit --amend --author "Kuzma Petrov-Vodkin <firstname.lastname@example.org>" # Now push the changes git push origin HEAD:master # Leave the detached head state git checkout master </pre></li> </ol> Return to Krita/FeatureBranchesWorkflow. Retrieved from "https://community.kde.org/Krita/FeatureBranchesWorkflow"