Skip to content

Commit 72dfd5e

Browse files
authored
Fix content issues for commonmark in "Pull requests" articles (#42137)
1 parent 5300043 commit 72dfd5e

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,11 +34,12 @@ If a site administrator disables the merge conflict editor for pull requests bet
3434

3535
![Screenshot of a warning that a pull request has a merge conflict. The "Resolve merge conflicts" button is outlined in dark orange.](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
3636

37-
{% note %}
37+
{% note %}
3838

39-
**Note:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)."
39+
**Note:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)."
40+
41+
{% endnote %}
4042

41-
{% endnote %}
4243
{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}
4344
1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict.
4445
1. Once you've resolved all the conflicts in the file, click **Mark as resolved**.

content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,11 +42,11 @@ People with write permissions to a repository can enable auto-merge for a pull r
4242
{% ifversion fpt %}
4343
1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit.
4444

45-
{% note %}
45+
{% note %}
4646

47-
**Note:** The email dropdown menu is not available if you have email privacy enabled or if you only have one verified and visible email associated with your {% data variables.product.company_short %} account.
47+
**Note:** The email dropdown menu is not available if you have email privacy enabled or if you only have one verified and visible email associated with your {% data variables.product.company_short %} account.
4848

49-
{% endnote %}
49+
{% endnote %}
5050
{% endif %}
5151
{% ifversion ghes or ghae or ghec %}
5252
1. If you chose the merge or squash and merge methods, type a commit message and description.

0 commit comments

Comments
 (0)