Revision as of 08:25, 11 June 2016 edit Dismine (talk \| contribs) Autopatrolled users, Bots, Confirmed users, Rollbackers 347 edits No edit summary ← Older edit		Revision as of 15:05, 12 June 2016 edit undo Dismine (talk \| contribs) Autopatrolled users, Bots, Confirmed users, Rollbackers 347 edits No edit summary Newer edit →
Line 17: * Be sure you use correct branch for your changes. '''This is the most popular mistake'''. For very small/trivial patches (contains only one commit) use the '''develop''' named branch directly. If it's your first pull request better do it in '''feature''' branch. For regular patches (contains several commits) you should use the branch '''feature''' ('''recommended way'''). Don't worry if repository already contains one. We can have as many as we need (so called anonymous branches, [http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/ A Guide to Branching in Mercurial]). See [[Hacking:Tools#Mercurial\|Mercurial useful commands]]. * Add correct description for your pull request. It should contain string "Resolved (or Fixed) issue #XXX. <Text of an issue description>". Where XXX is a number of issue in the Issue Tracker. Read more about [https://confluence.atlassian.com/bitbucket/resolve-issues-automatically-when-users-push-code-221451126.html Resolving issues automatically when push code]. * Don't forget to add your changes to file ChangeLog.txt.

Hacking:Making pull requests: Difference between revisions