lilith/tldr
1
0
Fork 0
mirror of https://github.com/tldr-pages/tldr.git synced 2025-03-28 21:16:20 +01:00
Code Activity

COMMUNITY-ROLES: fix usage of angle brackets (#2911)

Browse source 
Without wrapping in code spans using backticks,
angle brackets are interpreted as HTML tags,
and stripped out from the rendered version.
This commit is contained in:
Waldir Pimenta 2019-04-15 13:07:25 +01:00 • committed by Starbeamrainbowlabs
parent 6fe385b344
commit de2b04eb49
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
COMMUNITY-ROLES.md
View file

@ -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 #<issue number>" in the PR description.
Make sure to include `Closes #<issue number>` 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 #<issue number>" in the PR description.
Make sure to include `Closes #<issue number>` 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 #<issue number>" in the PR description.
Make sure to include `Closes #<issue number>` 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 #<issue number>" in the PR description.
Make sure to include `Closes #<issue number>` in the PR description.
The issue will then be automatically closed once the PR is merged.