Check daily for changes in published ASC API #201
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Code Coverage Report
Generated by 🚫 Danger Swift against 8e778f3 |
AvdLee
approved these changes
Aug 25, 2022
|
If you need some inspiration on how to create pull requests when the spec has changed, you can take a look at the script made for Bagbutik. |
|
Congratulations! 🎉 This was released as part of Release 2.3.0 🚀 Generated by GitBuddy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a workflow that will run daily and compare the contents of the currently-published ASC API spec (from https://developer.apple.com/sample-code/app-store-connect/app-store-connect-openapi-specification.zip) with the current contents of the HEAD branch. Any diffs will result in a workflow failure and notification, which will need to be address by manually updating the spec and re-generating the API (at least for now).
See discussion at: #197 (comment)
Note that the initial run will fail due to whitespace differences, which is a side-effect of using
jqto fix the missing enum case (also mentioned in #197).