refactor: introduce mnemonic convention for rules_lint linters #266
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
gregmagolan
force-pushed
the
mnemonic_convention
branch
from
3757869
to
c451fc5
Compare
gregmagolan
force-pushed
the
mnemonic_convention
branch
3 times, most recently
from
99306b9
to
b2633ba
Compare
gregmagolan
force-pushed
the
mnemonic_convention
branch
from
b2633ba
to
85c5507
Compare
alexeagle
approved these changes
May 30, 2024
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.
Standardize the mnemonic for linters in this repository to
AspectRulesLintFoobarso that we don't collide with other mnemonics and so that downstream tools that post-process generated report, patch and exit_code files can reliably determine the linter type using this convention.