Lines Matching refs:commit
10 had several contributions accepted, commit privileges are often quickly granted.
26 * [Git commit rules](#git-commit-rules)
103 should be credited, the `Co-authored-by` tag in the commit message may be used.
284 Your name will likely be included in the Git commit log. If your change affects
288 ## Git commit rules
290 This section refers to contributors that have Git push access and make commit
362 3. Do not commit multiple files and dump all messages in one commit. If you
363 modified several unrelated files, commit each group separately and provide a
364 nice commit message for each one. See example below.
366 4. Do write your commit message in such a way that it makes sense even without
371 5. In your commit messages, keep each line shorter than 80 characters. And try
377 The format of the commit messages is pretty simple.
384 An Example from the git project (commit 2b34e486bc):
388 It looks like commit 99fb6e04 (pack-objects: convert to use parse_options(),
392 If you fix some bugs, you should note the bug ID numbers in your commit message.
