Lines Matching refs:commit
30 - Avoid long commit series. If you do have a long series, consider whether some
32 - Make sure your commit messages are in the proper format. Please keep the 50/72 rule (for details …
37 …h multiple commits, you should make all documentation changes (and nothing else) in the last commit
38 of the series. Otherwise, include the documentation changes within the single commit.
58 - Ensure that each commit in the series has at least one ``Signed-off-by:`` line, using your real n…
60 …commit, they must also add their own ``Signed-off-by:`` line. By adding this line the contributor …
64 - Ensure that each commit also has a unique ``Change-Id:`` line. If you have cloned the repository …
65 commit-msg hook`" clone method, this should already be the case.
86 - If the changes are not based on a sufficiently-recent commit, or if they cannot be automatically …
90 …during integration, the merge commit will be removed from the ``integration`` branch and the :ref:…
100 .. _`Tim Popes blog entry`: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html