Amend no-code-in-heading rule as there is no clear consensus #22472
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SphinxKnight
requested review from
hamishwillee
and removed request for
a team
github-actions
bot
added
the
Content:Other
|
Preview URLs Flaws (1)URL:
|
Rumyra
approved these changes
Nov 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This update the style rule regarding
codeterms forbidden in headings to allow them "back".Motivation
After starting https://github.com/orgs/mdn/discussions/271, I found there was no clear consensus regarding this rule and decided to go a step further as I'm a proponent of having code terms marked as such in headings.
Related issues and pull requests
https://github.com/orgs/mdn/discussions/271
I didn't find any git history from the yari epoch.