Skip to content

Commit a3384b4

Browse files
authored
Merge pull request #50856 from lootle1/MR114
Technical Review 1055087: Settle competing commits by using merge con…
2 parents deaf22f + 74fa860 commit a3384b4

File tree

7 files changed

+13
-13
lines changed

7 files changed

+13
-13
lines changed

learn-pr/github/resolve-merge-conflicts-github/1-introduction.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Introduction
44
metadata:
55
title: Introduction
66
description: Learn to settle overlapping commits across branches by using merge conflict resolution.
7-
ms.date: 12/04/2023
7+
ms.date: 06/10/2025
88
author: a-a-ron
99
ms.author: aastewar
1010
ms.topic: unit

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: What are merge conflicts?
44
metadata:
55
title: What are merge conflicts?
66
description: Learn to settle overlapping commits across branches by using merge conflict resolution.
7-
ms.date: 12/04/2023
7+
ms.date: 06/10/2025
88
author: a-a-ron
99
ms.author: aastewar
1010
ms.topic: unit

learn-pr/github/resolve-merge-conflicts-github/3-manage-merge-conflicts.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Exercise - Manage merge conflicts
44
metadata:
55
title: Exercise - Manage merge conflicts
66
description: Learn to settle overlapping commits across branches by using merge conflict resolution.
7-
ms.date: 12/04/2023
7+
ms.date: 06/10/2025
88
author: a-a-ron
99
ms.author: aastewar
1010
ms.topic: unit

learn-pr/github/resolve-merge-conflicts-github/4-knowledge-check.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Module assessment
44
metadata:
55
title: Module assessment
66
description: Check your knowledge about merge conflict resolution.
7-
ms.date: 12/04/2023
7+
ms.date: 06/10/2025
88
author: a-a-ron
99
ms.author: aastewar
1010
ms.topic: unit

learn-pr/github/resolve-merge-conflicts-github/5-summary.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ uid: learn.github.merge-conflict-resolution-github.5-summary
33
title: Summary
44
metadata:
55
title: Summary
6-
description: Review what you've learned.
7-
ms.date: 12/04/2023
6+
description: Review what you learned.
7+
ms.date: 06/10/2025
88
author: a-a-ron
99
ms.author: aastewar
1010
ms.topic: unit

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: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
### YamlMime:Module
22
uid: learn.github.merge-conflict-resolution-github
33
metadata:
4-
title: "Settle competing commits by using merge conflict resolution on GitHub"
4+
title: "Settle Competing Commits by Using Merge Conflict Resolution on GitHub"
55
description: Learn to settle overlapping commits across branches by using merge conflict resolution.
6-
ms.date: 12/04/2023
6+
ms.date: 06/10/2025
77
author: a-a-ron
88
ms.author: aastewar
99
ms.topic: module
1010
ms.service: github
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)