-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
ci: Add CI check for Parse Server options definitions #7955
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
Conversation
Thanks for opening this pull request!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #7955 +/- ##
==========================================
+ Coverage 93.82% 94.25% +0.42%
==========================================
Files 182 180 -2
Lines 13629 13987 +358
==========================================
+ Hits 12787 13183 +396
+ Misses 842 804 -38 ☔ View full report in Codecov by Sentry. |
Not quite sure why this runs fine locally but github actions responds with |
Likely because in the GH container environment the path root is different from your local env. |
Ok, thanks for the pointers CI expert! If you could have a quick look at the approach and let me know your general thoughts some time that would be great. |
resources/checkDefinitions.js
Outdated
} else { | ||
process.exit(0); | ||
} | ||
})(); |
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.
Could you use const core = require('@actions/core');
and in addition to logging a console.log
use core.error
. See the existing checks in /ci
directory. IIRC I've kept the console.log
logging only for debug purposes because core
logs are not displayed locally. That core lib is quite convenient, you can define for example what is displayed as the main error for the failing CI job in the CI summary.
59215e6
to
e6d7d8f
Compare
* return correct response when revert is used in beforeSave ([parse-community#7839](parse-community#7839)) ([f63fb2b](parse-community@f63fb2b))
077ee40
to
6b09c20
Compare
…se-server into definitions-ci-check
…se-server into definitions-ci-check
…se-server into definitions-ci-check
I will reformat the title to use the proper commit message syntax. |
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.
That's a very cool one! Will save us a quite some trouble in the future.
🎉 This change has been released in version 6.0.0-alpha.15 |
🎉 This change has been released in version 6.0.0-beta.1 |
🎉 This change has been released in version 6.0.0 |
New Pull Request Checklist
Issue Description
Often, the definitions files are manually edited.
Closes: #7918
Approach
Generates definitions and compares to committed definitions
TODOs before merging