Skip to content

Commit b4f3222

Browse files
committed
Line edits
1 parent f8a7fb4 commit b4f3222

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

learn-pr/github/resolve-merge-conflicts-github/includes/2-what-are-merge-conflicts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,4 +55,4 @@ In addition to mitigating the impact of merge conflicts, pulling updates also al
5555

5656
The `git rebase` (or `git pull --rebase`) command rewrites your branch history to use the current HEAD commit of the base branch as its base. In other words, your branch is updated to behave as though it were only branched from the current state of the base branch. This rebase means that all of your changes are compared to the latest state of the base branch, and not the original commit you originally branched from. Rebasing can make history easier to track after your eventual merge, because your commits will follow the previous parallel commits in a linear fashion. It's a good practice to rebase your branch immediately prior to merging upstream.
5757

58-
Learn more [about Git rebase](https://docs.github.com/get-started/using-git/about-git-rebase) and [resolving merge conflicts after a Git rebase](https://docs.github.com/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase).
58+
Learn more [about Git rebase](https://docs.github.com/get-started/using-git/about-git-rebase) and [resolving merge conflicts after a Git rebase](https://docs.github.com/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase).

learn-pr/github/resolve-merge-conflicts-github/index.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,10 @@ metadata:
1111
title: "Settle competing commits by using merge conflict resolution on GitHub"
1212
summary: Learn to settle overlapping commits across branches by using merge conflict resolution.
1313
abstract: |
14-
In this module, you will:
15-
- Understand how merging happens and what causes merge conflicts
16-
- Resolve simple and complex merge conflicts with ease
17-
- Share best practices to reduce merge conflicts with your team
14+
In this module, you'll:
15+
- Understand how merging happens and what causes merge conflicts.
16+
- Resolve simple and complex merge conflicts with ease.
17+
- Share best practices to reduce merge conflicts with your team.
1818
prerequisites: |
1919
- A GitHub account
2020
- The ability to navigate and edit files in GitHub

0 commit comments

Comments
 (0)