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(rulesets): add unused components server rule #2097
feat(rulesets): add unused components server rule #2097
Conversation
@jonaslagoni assuming you've received an invite and accepted it (which seems like you do according to what GH settings page tells me), perhaps create a branch in the Spectral repo itself? |
Haha, alright, I'll try to remember. It's just the standard we apply under AsyncAPI and the one that creates less clutter in upstream 😄 I was wondering why the jobs was not picked up by the CI 😅 |
Well, you can use the fork if that's how you approach it. I just wanted to let you know you can create branches here too, but it's not compulsory by any means, so you can continue to use the fork if that's how you do things.
It should work just fine and it usually does, but for some reason, it got stuck this time around. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like I'll need to merge this one cause of the CI.
LMK when you're good with the change, and I'll do it.
it's 👌 from my side
Fine by me yea 👍 |
# [@stoplight/spectral-rulesets-v1.7.0](https://github.com/stoplightio/spectral/compare/@stoplight/spectral-rulesets-v1.6.0...@stoplight/spectral-rulesets-v1.7.0) (2022-03-24) ### Features * **rulesets:** add unused components server rule ([#2097](#2097)) ([71b312e](71b312e))
🎉 This PR is included in version @stoplight/spectral-rulesets-v1.7.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
Partly solves #1103
Checklist
Does this PR introduce a breaking change?