Lines Matching refs:commit
102 it (or commit it directly if applicable).
224 All contributors with commit access to the LLVM Project are eligible to be a
225 maintainer. However, we are looking for people who can commit to:
303 discretion, preferably as part of the commit landing the changes. Examples of
377 progress. The developer is welcome to re-commit the change after the problem has
385 Although we don't enforce the format of commit messages, we prefer that
399 * Separate the commit message into title and body separated by a blank line.
401 * If you're not the original author, ensure the 'Author' property of the commit is
404 ``git commit --amend --author="John Doe <jdoe@llvm.org>"`` to correct the
411 <https://github.blog/2018-01-29-commit-together-with-co-authors/>`_.
420 or "[OpenMP] ...". This helps email filters and searches for post-commit
433 * If the commit is a bug fix on top of another recently committed patch, or a
434 revert or reapply of a patch, include the git commit hash of the prior
435 related commit. This could be as simple as "Revert commit NNNN because it
444 * It is also acceptable to add other metadata to the commit message to automate
447 such links and/or metadata should not be used in place of making the commit
472 original commit thread with the reverting patch author.
481 * If a test case that demonstrates a problem is reported in the commit thread,
483 * If you receive substantial :ref:`post-commit review <post_commit_review>`
503 the commit thread asking for assistance. We aren't trying to enumerate
509 * The commit message for the reverting commit should explain why patch
511 * It is customary to respond to the original commit email mentioning the
515 Where possible, we encourage sharing of test cases in commit threads, or
531 we encourage you to reply to the commit thread, give the author a bit to
534 * When re-applying a reverted patch, the commit message should be updated to
542 We grant commit access to contributors that can provide a valid justification.
543 If you would like commit access, please use this `link <https://github.com/llvm/llvm-project/issues/new?title=Request%20Commit%20Access%20For%20%3Cuser%3E&body=%23%23%23%20Why%20Are%20you%20requesting%20commit%20access%20?>`_ to file
544 an issue and request commit access. Replace the <user> string in the title
545 with your github username, and explain why you are requesting commit access in
549 you accept the invitation, you'll get commit access.
551 Prior to obtaining commit access, it is common practice to request that
552 someone with commit access commits on your behalf. When doing so, please
554 property of the commit.
557 on a commits mailing list soon after the commit lands (e.g. llvm-commits_).
559 commit to require a moderator to approve the email, so do not be concerned if a
560 commit does not immediately appear in the archives.
562 If you have recently been granted commit access, these policies apply:
564 #. You are granted *commit-after-approval* to all parts of LLVM. For
566 When approved, you may commit it yourself.
568 #. You are allowed to commit patches without approval which you think are
576 highly localized and the commit message should clearly state that the commit
580 #. You are allowed to commit patches without approval to those portions of LLVM
587 cause commit access to be revoked.
681 commit access may commit it for the author once appropriate (based on the
687 file describes higher-level contributions. If you commit a patch for someone
689 by the `commit messages`_ section. Overall, please do not add contributor names
692 Also, don't commit patches authored by others unless they have submitted the
695 etc.). The author should first submit them to the relevant project's commit
702 in a separate line of the commit message and there are automated processes that
842 *If your commit broke the build:*
855 * Revert the commit if this blocks your work, see revert_policy_ .