Lines Matching refs:commit

96 developer. In the commit message of the contribution, (described more fully
136 The "sign-off" in the DCO is a "Signed-off-by:" line in each commit's log
147   author the commit (CI will fail if there is no match)
149 You can automatically add the Signed-off-by: line to your commit body using
150 ``git commit -s``. Use other commits in the zephyr git history as examples.
156 - If you are altering an existing commit created by someone else, you must add
160   commit by running ``git commit --amend -s``.
174 * the cherry-picked commits or portions of a commit shall preserve the original
378 Changes are submitted as Git commits. Each commit has a *commit
379 message* describing the change. Acceptable commit messages look like
391 fit your commit.
398 Here is an example of a good commit message.
414 This line is called the commit's *title*. Titles must be:
450    An empty commit message body is not permitted. Even for trivial
451    changes, please include a descriptive commit message body. Your
454 This part of the commit should explain what your change does, and why
463 Each line in your commit message should usually be 75 characters or
467 For examples of accepted commit messages, you can refer to the Zephyr GitHub
477    already. Create your commit with ``git commit -s`` to add the
480 For open source licensing reasons, your commit must include a
499 in the Git commit's ``Author:`` field.
510 Do not include `GitHub references`_ in the commit message directly, as it can
567 code, make the file *$ZEPHYR_BASE/.git/hooks/pre-commit* executable and edit
576 Instead of running checkpatch at each commit, you may prefer to run it only
634 * Git commit formatting
642 PR is created, and again every time the PR is modified with a commit.
829      git commit -s
831    The ``-s`` option automatically adds your ``Signed-off-by:`` to your commit
832    message.  Your commit will be rejected without this line that indicates your
833    agreement with the :ref:`DCO`.  See the :ref:`commit-guidelines` section for
834    specific guidelines for writing your commit messages.
846    request for the ``main`` branch. The title and message from your commit
874    commit(s) to fix review issues. In your development repo::
876      git rebase -i <offending-commit-id>^
879    a specific commit (if there's more than one in your pull request), or
880    remove the line to delete a commit entirely.  Then edit files to fix the
889    Update commit comment if needed, and continue::
985 cases where the file is an original to Zephyr, the commit message should
992 <external-contributions>`, the commit message shall contain details regarding
994 commit for the file and the intended purpose.
1001       commit: 853207acfdc6549b10eb3e44504b1a75ae1ad63a
1009       commit: 08ded7f21529c39e5133688ffb93a9d0c94e5c6e
1078   of version 2 (see commit `262cc55609
1079   <https://github.com/zephyrproject-rtos/zephyr/commit/262cc55609b73ea61b5f999c6c6daaba20bc5240>`_)
1082   <https://github.com/zephyrproject-rtos/zephyr/commit/6bf761fc0a2811b037abec0c963d60b00c452acb>`_)