📖 Set GitLab support for Code-Review and Dependency-Update-Tool#4963
Closed
📖 Set GitLab support for Code-Review and Dependency-Update-Tool#4963
Conversation
Following the discussion in ossf#4795 (comment) Signed-off-by: Diogo Correia <diogo.correia@siemens.com>
dosubot
bot
added
the
size:S
|
This pull request has been marked stale because it has been open for 10 days with no activity |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Following the discussion in #4795 (comment), it updates the checks documentation to advertise GitLab support for
Code-ReviewandDependency-Update-Tool.What is the current behavior?
Scorecard supports
Code-ReviewandDependency-Update-Toolagainst GitLab but it wrongly documented.What is the new behavior (if this is a feature change)?**
No change in behavior.
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
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.)