Mark PRs with nonNpm as Check Config#1187
Closed
jakebailey wants to merge 4 commits into
Closed
Conversation
sandersn
approved these changes
Jul 11, 2025
sandersn
left a comment
sandersn
left a comment
Member
There was a problem hiding this comment.
Check Config means that a maintainer must approve it, right?
Member
Author
|
No, I don't think it has that effect. Will check |
Member
Author
|
It would. Nevermind. |
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.
People still try to contribute packages which go against https://github.com/DefinitelyTyped/DefinitelyTyped#what-about-type-definitions-with-no-matching-package
Probably worth flagging
nonNpmpackages asCheck Config.