Confirmed users
1,927
edits
Bugzilla:Committing Patches: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
Note that the description given on the commit comment should describe what the patch actually ''does'' (in a broad sense), which may not necessarily match the summary of the bug being fixed. For example, of the summary of the bug is "Bugzilla doesn't do Foo", then your description in the commit comment should say something like "Make Bugzilla do Foo". | Note that the description given on the commit comment should describe what the patch actually ''does'' (in a broad sense), which may not necessarily match the summary of the bug being fixed. For example, of the summary of the bug is "Bugzilla doesn't do Foo", then your description in the commit comment should say something like "Make Bugzilla do Foo". | ||
If you are committing the patch on behalf of someone else, such as a contributor without write access, use the --author option to "git commit" to indicate this, e.g. --author="Somebody Else <somebody@example.com>". | |||
Once you've [http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository committed] or [http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging#Basic-Merging merged] to the right branch (usually master) of your local clone, you are ready to push it to git.mozilla.org. Write access is via ssh. Assuming you have already cloned it via the read-only https protocol, you can either add a new remote or update an existing remote: | Once you've [http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository committed] or [http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging#Basic-Merging merged] to the right branch (usually master) of your local clone, you are ready to push it to git.mozilla.org. Write access is via ssh. Assuming you have already cloned it via the read-only https protocol, you can either add a new remote or update an existing remote: | ||