apifellows/OAS3 Linter
Validates Open API Specification (OAS3) YAML files using @apifellows Linter
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Nov 4, 2025
- License
- None
Pinned Snippet
uses: apifellows/gha-linter-oas3@f72b73319dd1b99750e0716ea93df2b86017fa26 # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| file-path | Path to the OpenAPI 3 YAML file in your repository to validate | yes | — |
| continue-on-specification-error | Continue CI/CD execution if the specification validation fails (true/false) | no | false |
| continue-on-server-error | Continue CI/CD execution if @apifellows service has an error or is unavailable (true/false) | no | false |
| version | @apifellows OAS3 Linter Version (e.g., v1, v2) | no | v1 |
Outputs
| name | description |
|---|---|
| result | Validation result (success, warning, error) |
| status-code | HTTP status code from the API |