-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Custom Rulesets in GitHub Action #327
Labels
Comments
philsturgeon
assigned philsturgeon and XVincentX and unassigned philsturgeon and XVincentX
Jul 15, 2019
@nulltoken I've changed the priority of this one to highest. Can you help us out with this? I set it to medium back in Oct but that meant it got ignored by everyone lol |
@nulltoken started a PR on the README, can you take this over. stoplightio/spectral-action#129 |
This has been done over on the repo! From now on the action and spectral will be much closer to being in sync. Team DevRel on the case! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story
As a slightly technical user who is dipping my toe into the world of API Specs, I would like to get feedback in PRs about my specs, and I want that to be as easy as possible, so enabling a GitHub Action and having the whole thing done would be perfect.
Details
We have a GitHub Action: https://github.com/stoplightio/spectral-action which is stuck on Spectral v4. We need to upgrade it to v5.x, improve the README so its obvious how it works, and make it look for spectral rulesets in the root.
We should also document it. I think taking this section:
and turning it into an "Automation & CI" guide, would mean we can show how it works with CircleCI and GitHub Actions, and folks can use one of those two approaches for inspiration for other CI implementations.
Test out any instructions you write down! 😅
Acceptance Criteria
.spectral.{json|yml|yaml}
in the root folder like the CLI / Studio doesOut of Scope
Custom rules, custom functions, multiple rulesets, etc.
The text was updated successfully, but these errors were encountered: