-
Notifications
You must be signed in to change notification settings - Fork 254
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
feat(build): add dependency check to CI workflow #3276
feat(build): add dependency check to CI workflow #3276
Conversation
300f12d
to
9cabe63
Compare
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #3276 +/- ##
=======================================
Coverage 66.06% 66.06%
=======================================
Files 843 843
Lines 16937 16937
Branches 938 938
=======================================
Hits 11190 11190
Misses 5377 5377
Partials 370 370 ☔ View full report in Codecov by Sentry. |
0b346e5
to
8a88124
Compare
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.
great stuff
still waiting for some IPlab approvals. Once they are in, i'll update the PR and move to review. |
4c8f694
to
5341960
Compare
35af1fe
to
0012457
Compare
0012457
to
eaed861
Compare
* feat(build): add dependency check to CI workflow * removed script, updated docs * update * moved dependency checks to its own workflow * approvals of some libs
What this PR changes/adds
DEPENDENCIES
file, which is referenced from NOTICE.md to enable easy automatic processingWhenever there is a new dependency, or a new version of an existing dependency, the DEPENDENCIES file must be regenerated. If the dependency is not yet reviewed, an IPLab issue must be opened, to get an
approved
status. This should be done manually.If there is a
rejected
dependency, the CI job will fail.Why it does that
EF requirements
Further notes
.github
repoLinked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.