-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(tools): introduce generic generator for various repo checks #22332
Comments
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
nx shipped new core feature that will help us achieve these things in official way via generators |
Story 🧚♀️
Currently we don't have a common way how to write various local/CI checks, so we don't put repo into invalid state by accident.
Idea is to create pluggable solution with tests that we have confidence that things work.
The solution will be implemented as a pluggable nx generator
API proposal
where:
validate-repo
name of generator--codeowners
boolean flag that will run codeowners setup check--pr-size=30
configurable flag that will run PR size check and will break CI if user changed more than 30 filestasks
Related issues
The text was updated successfully, but these errors were encountered: