Lines Matching refs:commit

67 self-contained commit initially.
69 provide feedback. It also helps maintain a clear and organized commit history
73 Create a local branch per commit you want to submit and then push that branch
77 As GitHub uses the first line of the commit message truncated to 72 characters
107 `built-in support for fixups <https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---fixupamendrewordltcommitgt>`_
111 you must use the pull request title and description as the commit message.
157 If the PR is a single commit, all you need to do is click the merge button in
161 one commit. There are three different ways to do this, shown here with the most
165   remember to review the commit message when prompted.
172   commit message and check that the final commit looks as you expect. When
243 Even though your PR passed the pre-commit checks and is approved by reviewers, it
288   # Commit, use a good commit message
289   git commit file.cpp
301   git commit file.cpp -m "Code Review adjustments"
307   git commit -a --amend
373   # Commit, use a good commit message
374   git commit file.cpp
393   git commit file.cpp -m "Code Review adjustments"
399   git commit -a --amend
447   /cherry-pick <commit> <commit> <...>
449 This command takes one or more git commit hashes as arguments and will attempt
450 to cherry-pick the commit(s) to the release branch.  If the commit(s) fail to
452 the issue/pull request.  If the commit(s) do apply cleanly, then a pull request
455 If a commit you want to backport does not apply cleanly, you may resolve