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.
286 Your name will likely be included in the Git commit log. If your change affects
290 ## Git commit rules
292 This section refers to contributors that have Git push access and make commit
363 3. Do not commit multiple files and dump all messages in one commit. If you
364 modified several unrelated files, commit each group separately and provide a
365 nice commit message for each one. See example below.
367 4. Do write your commit message in such a way that it makes sense even without
372 5. In your commit messages, keep each line shorter than 80 characters. And try
378 The format of the commit messages is pretty simple.
385 An Example from the git project (commit 2b34e486bc):
389 It looks like commit 99fb6e04 (pack-objects: convert to use parse_options(),
393 If you fix some bugs, you should note the bug ID numbers in your commit message.