OpenAPITools / OpenAPITools/openapi-diff
Add official Github action for openapi-diff
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
Openapi-diff is well suited to be integrate into Github actions in order to:
- Highlight breaking in a pull request
- Document changes in OpenAPI
- etc.
For example, today we have an internal github repo which on every commit triggers generating Redoc OpenAPI documentation and publishes it to Github pages for the repository. In this documentation we'd like to include a openapi-diff markdown report of the changes.
Or, when ever we do a pull request we want to review the changes made. Openapi-diff will allow us to identify automatically breaking changes.
There are a couple of unofficial limited Github actions based on other openapi diff tool
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing entry points and release or automation configuration; the issue names no files or tests. Compare the requested behavior with the linked unofficial actions and determine how an official action should expose OpenAPI diff results and breaking-change checks. Done means a usable GitHub Action is documented and validated for pull-request and report-generation workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java, openapi
- Domain
- api, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100