✨ Add Azure Devops to CI checks #2662
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
pettermk
requested review from
azeemshaikh38,
justaugustus,
laurentsimon,
naveensrinivasan and
spencerschrock
as code owners
pettermk
had a problem deploying
to
integration-test
GitHub Actions
Failure
pettermk
force-pushed
the
#2661-add-azure-devops-to-ci-checks
branch
from
a2edadc
to
7b9f0dd
Compare
pettermk
had a problem deploying
to
integration-test
GitHub Actions
Failure
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 |
pettermk
force-pushed
the
#2661-add-azure-devops-to-ci-checks
branch
from
7b9f0dd
to
22eca4a
Compare
pettermk
had a problem deploying
to
integration-test
GitHub Actions
Failure
Thank you, scorecard is very useful! |
pettermk
requested review from
naveensrinivasan
and removed request for
justaugustus,
azeemshaikh38,
spencerschrock and
laurentsimon
naveensrinivasan
force-pushed
the
#2661-add-azure-devops-to-ci-checks
branch
from
22eca4a
to
ab96f13
Compare
naveensrinivasan
had a problem deploying
to
integration-test
GitHub Actions
Failure
raghavkaul
approved these changes
Feb 16, 2023
pettermk
had a problem deploying
to
integration-test
GitHub Actions
Failure
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com>
naveensrinivasan
force-pushed
the
#2661-add-azure-devops-to-ci-checks
branch
from
4d34f95
to
8e61c4d
Compare
naveensrinivasan
temporarily deployed
to
integration-test
GitHub Actions
Inactive
Shofiya2003
pushed a commit
to Shofiya2003/scorecard
that referenced
this pull request
Mar 10, 2023
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com> Signed-off-by: Shofiya2003 <shofiyabootwala@gmail.com>
Shofiya2003
pushed a commit
to Shofiya2003/scorecard
that referenced
this pull request
Mar 10, 2023
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com> Signed-off-by: Shofiya2003 <shofiyabootwala@gmail.com>
raghavkaul
pushed a commit
to raghavkaul/scorecard
that referenced
this pull request
Apr 4, 2023
Fixes ossf#2661 Signed-off-by: Petter Kvalvaag <pmkv@equinor.com>
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.
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.)