Disable rumdl rules triggered by CoC edit warning.#300
Merged
freakboy3742 merged 1 commit intobeeware:mainfrom Feb 16, 2026
Merged
Disable rumdl rules triggered by CoC edit warning.#300freakboy3742 merged 1 commit intobeeware:mainfrom
freakboy3742 merged 1 commit intobeeware:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
rumdl is triggering in the target repositories because the injected warning is violating various rumdl rules.
This will resolve the issue in all target repositories without needing to change the configuration there.
Tested the change by temporarily adding it to the
CODE_OF_CONDUCT.mdfile in beeware-docs-tools, and runningpre-commit. It passes with these changes.PR Checklist: