Difference between revisions of "Git Guidelines"

From Minetest Developer Wiki
Jump to navigation Jump to search
(Created page with "For instructions on basic usage, see Git. == Upstream commit rules == # You can push something to upstream [1] only if some other member of the core development team agr...")
 
Line 14: Line 14:
 
[2] The team: https://github.com/minetest?tab=members
 
[2] The team: https://github.com/minetest?tab=members
  
[3] For a github pull request, this is easiest done by appending .patch to the pull request URL, wgetting it to your project directory and doing <code>git am whatever.patch</code>.
+
[3] For a github pull request, this is easiest done by appending .patch to the pull request URL, wgetting it to your project directory and doing <code>git am whatever.patch</code>. Similarly for single commits.

Revision as of 19:37, 23 March 2013

For instructions on basic usage, see Git.

Upstream commit rules

  1. You can push something to upstream [1] only if some other member of the core development team agrees on it [2]
  2. Commit messages must look good and be in the present tense (look at the commit log)
  3. Do not modify history older than 10 minutes
  4. Use rebase, not merge, to get linear history. [3]

Notes

[1] Upstream is at https://github.com/minetest

[2] The team: https://github.com/minetest?tab=members

[3] For a github pull request, this is easiest done by appending .patch to the pull request URL, wgetting it to your project directory and doing git am whatever.patch. Similarly for single commits.