-
Notifications
You must be signed in to change notification settings - Fork 504
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
✨ Add Azure Devops to CI checks #2662
✨ Add Azure Devops to CI checks #2662
Conversation
a2edadc
to
7b9f0dd
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.
Thanks!
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2662 +/- ##
=======================================
Coverage 41.27% 41.27%
=======================================
Files 123 123
Lines 10043 10043
=======================================
Hits 4145 4145
Misses 5602 5602
Partials 296 296 |
7b9f0dd
to
22eca4a
Compare
Thank you, scorecard is very useful! |
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.
Thank you!
22eca4a
to
ab96f13
Compare
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com>
4d34f95
to
8e61c4d
Compare
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com> Signed-off-by: Shofiya2003 <shofiyabootwala@gmail.com>
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com> Signed-off-by: Shofiya2003 <shofiyabootwala@gmail.com>
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com>
What kind of change does this PR introduce?
Adds Azure Devops as a valid CI system when running the CI check
What is the current behavior?
Repos that are tested with Azure Devops get 0 as a score, as it is not recognized
What is the new behavior (if this is a feature change)?**
Repos that are tested with Azure Devops are not penalized
Which issue(s) this PR fixes
Fixes #2661
Special notes for your reviewer
I removed an entry as well, as it did not seem to possibly have any effect and also had
no tests associated
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)