Lines Matching refs:commit

16 [Change-Id commit-msg hook](https://gerrit-documentation.storage.googleapis.com/Documentation/2.14.…
17 This adds a `Change-Id` line to each commit message locally, which Gerrit uses
21 To download the commit-msg hook for the Open Screen repository, use the
25   curl -Lo .git/hooks/commit-msg https://chromium-review.googlesource.com/tools/hooks/commit-msg
26   chmod a+x .git/hooks/commit-msg
44 in each commit.
47 commit, and therefore a new change.  Gerrit's documentation for
50 it should contain the matching `Change-Id` line in the commit message.
54 By default, each commit to your local branch will get its own Gerrit change when
63   git commit --amend
67 to attach the current `Change-Id` to the most recent commit. Check that the
72 commit with the correct Change-Id:
80 existing commit that has been uploaded for review.
87 of the commit you are pushing has a Change-Id line, that change will also be the
91 To put this into an example, let's say you have a commit for feature A with
101   git commit
117 commit 47525d663586ba09f40e29fb5da1d23e496e0798 (HEAD -> featureB)
123 commit 167a541e0a2bd3de4710965193213aa1d912f050 (featureA)
160 lines in them (this can be done with the [commit-msg
161 hook](https://gerrit-documentation.storage.googleapis.com/Documentation/2.14.7/cmd-hook-commit-msg.…
173 # it.  You can git commit --amend with the commit-msg hook active or add it via
174 # git commit --amend after pushing.  Don't git commit --amend after creating N
201 (commit P) and feature B being rebased onto A, then uploaded to Gerrit as commit