From de2b04eb49d0f9f23b1c5f320be1bc3686667ec8 Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Mon, 15 Apr 2019 13:07:25 +0100 Subject: [PATCH] COMMUNITY-ROLES: fix usage of angle brackets (#2911) Without wrapping in code spans using backticks, angle brackets are interpreted as HTML tags, and stripped out from the rendered version. --- COMMUNITY-ROLES.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/COMMUNITY-ROLES.md b/COMMUNITY-ROLES.md index afa6eddc5..8f8d65a98 100644 --- a/COMMUNITY-ROLES.md +++ b/COMMUNITY-ROLES.md @@ -113,7 +113,7 @@ using one of the template messages below as a base. 3. Open a PR adding their name to the "Current repository collaborators" section in [MAINTAINERS.md](MAINTAINERS.md). - Make sure to include "Closes #" in the PR description. + Make sure to include `Closes #` in the PR description. The issue will then be automatically closed once the PR is merged. ### Adding new organization members @@ -138,7 +138,7 @@ using one of the template messages below as a base. 3. Open a PR moving their name to the "Current organization members" section in [MAINTAINERS.md](MAINTAINERS.md). - Make sure to include "Closes #" in the PR description. + Make sure to include `Closes #` in the PR description. The issue will then be automatically closed once the PR is merged. ### Adding new organization owners @@ -164,7 +164,7 @@ using one of the template messages below as a base. 3. Open a PR moving their name to the "Current organization owners" section in [MAINTAINERS.md](MAINTAINERS.md). - Make sure to include "Closes #" in the PR description. + Make sure to include `Closes #` in the PR description. The issue will then be automatically closed once the PR is merged. ### Removing inactive organization members @@ -191,7 +191,7 @@ using one of the template messages below as a base. 3. Open a PR moving their name to the "Past organization owners" section in [MAINTAINERS.md](MAINTAINERS.md). - Make sure to include "Closes #" in the PR description. + Make sure to include `Closes #` in the PR description. The issue will then be automatically closed once the PR is merged.