Fix Emoji URLs
What does this MR do?
This MR intends to fix the broken Emoji's on GitLab Markdown: Emoji introduced in d07919de.
Related issues
Closes #59139 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the ~Documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Merge request reports
Activity
added documentation label
mentioned in merge request !26309 (closed)
mentioned in issue #59139 (closed)
added Plan [DEPRECATED] devopsplan markdown typebug labels
1 Warning This merge request does not refer to an existing milestone. 1 Message This merge request adds or changes files that require a review from the Technical Writing team. Documentation review
The following files require a review from a technical writer:
doc/user/markdown.md
The review does not need to block merging this merge request. See the:
- DevOps stages for the appropriate technical writer for this review.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has randomly picked a candidate for each review slot. Feel free to override this selection if you think someone else would be better-suited, or the chosen person is unavailable.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not (yet?) automatically notify them for you.
Category Reviewer Maintainer ~Documentation Mike Lewis ( @mikelewis
)Generated by
DangerEdited by 🤖 GitLab Bot 🤖marked the checklist item Follow the Documentation Guidelines and Style Guide. as completed
added Support Team Contributions label
changed milestone to %11.10
mentioned in commit 9dd5cb9b
mentioned in issue #59980 (closed)
mentioned in issue gitlab-org/release/tasks#731 (closed)
Thank you @dcoy1! Mind if I ask you to please avoid mentioning the entire
@gl\-docsteam
unless it's something that concerns us all? It creates tons of todos that we don't have to take any action for. Please assign MRs to us according to the tech writer assigned to each devops stage.Edited by Marcia Ramosassigned to @eread