devops: switch to @tony.ganchev/eslint-plugin-header#2031
Open
tonyganchev wants to merge 1 commit intoIBM:mainfrom
Open
devops: switch to @tony.ganchev/eslint-plugin-header#2031tonyganchev wants to merge 1 commit intoIBM:mainfrom
tonyganchev wants to merge 1 commit intoIBM:mainfrom
Conversation
Reasons: - The fork is supported and updated. - ESLint 9-native with full schema support and needing no hacks. - Windows support - Multiple other bugfixes. - UX improvements - better error messages and more autofix capabilities. - Extensive documentation. - Better configuration format (although the old one is still supported). Signed-off-by: Tony Ganchev <tony.ganchev@gmail.com>
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
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.
PR summary
Reasons:
Fixes: (not sure if non-maintainers should spam with devops issues).
PR Checklist
Please make sure that your PR fulfills the following requirements:
Angular Commit Message Guidelines.
PR Type
What is the current behavior?
N/A
What is the new behavior?
N/A
Does this PR introduce a breaking change?
Other information