chore: exclude examples from renovate #1460
Merged
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
dyladan
approved these changes
Apr 5, 2023
Contributor
Member
Author
|
Sorry, can't remember for sure. Long time ago husky was used to avoid malformed commits already in user repo via husky. That was terrible annoying and therefore removed. e.g. there is anyway no need to have validated commit message on each commit because we squash during integration and commits done in browser skipped the check. I think in core repo a CI lint step checks the commit message meanwhile but contrib repo tends to be behind regarding tooling. I guess there are some leftovers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Exclude examples from renovate runs because there is no CI to verify that they still work after the update.
As they are terrible outdated already any update is likely breaking them because some still use components not released anymore and therefore no compatibility to actual release without code change.
Refs: #1459