You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-15Lines changed: 9 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,29 +14,23 @@ _Learn why conflicts happen and how to resolve them._
14
14
</header>
15
15
16
16
<!--
17
-
<<< Author notes: Step 3 >>>
17
+
<<< Author notes: Step 4 >>>
18
18
Start this step by acknowledging the previous step.
19
19
Define terms and link to docs.github.com.
20
20
-->
21
21
22
-
## Step 3: Create your own conflict
22
+
## Step 4: Merge your pull request
23
23
24
-
_Good job! You've solved a merge conflict! :tada:_
24
+
_Almost there! :heart:_
25
25
26
-
Resolving a conflict doesn't automatically merge the pull request in GitHub. Instead, it stores the resolution of the conflict in a merge commit and allows you and your team to keep working. To resolve a conflict, GitHub performs what is known as a _reverse merge_. This means that the changes from the `main` branch were merged into your `my-resume` branch. With a reverse merge, only the `my-resume` branch is updated. This allows you to test the resolved changes on your branch before you merge it into `main`.
26
+
You can now [merge](https://docs.github.com/en/get-started/quickstart/github-glossary#merge)your pull request!
27
27
28
-
Now, let's get a little evil. (It's for educational purposes!)
28
+
### :keyboard: Activity: Merge your pull request
29
29
30
-
### :keyboard: Activity: Create your own conflict
31
-
32
-
We went ahead and added a new file called `references.md` and pushed that change to `main`, without updating your `my-resume` branch.
33
-
34
-
1. Browse to the `my-resume` branch.
35
-
1. Click the `Add file` dropdown menu and then on `Create new file`.
36
-
1. Create a file named `references.md`.
37
-
1. Enter some text that conflicts with what we added for `references.md` in the `main` branch.
38
-
1. Scroll to the bottom of the page and enter a commit message for your change.
39
-
1. Click the **Commit new file** button, making sure the "Commit directly to the `my-resume` branch" option is selected.
30
+
1. First, resolve any remaining conflicts in your pull request.
31
+
> Look back at step one if you need help.
32
+
1. Click **Merge pull request**.
33
+
1. Delete the branch `my-resume` (optional).
40
34
1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
0 commit comments