Skip to content
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 woodpecker as known CI #4336

Merged
merged 3 commits into from
Sep 11, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/checks.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ number of vulnerabilities that find their way into a project.
The check works by looking for a set of CI-system names in GitHub `CheckRuns`
and `Statuses` among the recent commits (~30). A CI-system is considered
well-known if its name contains any of the following: appveyor, buildkite,
circleci, e2e, github-actions, jenkins, mergeable, test, travis-ci.
circleci, e2e, github-actions, jenkins, mergeable, test, travis-ci, woodpecker.

Note: A project that fulfills this criterion with other tools may still receive
a low score on this test. There are many ways to implement CI testing, and it is
Expand Down
2 changes: 1 addition & 1 deletion docs/checks/internal/checks.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,7 @@ checks:
The check works by looking for a set of CI-system names in GitHub `CheckRuns`
and `Statuses` among the recent commits (~30). A CI-system is considered
well-known if its name contains any of the following: appveyor, buildkite,
circleci, e2e, github-actions, jenkins, mergeable, test, travis-ci.
circleci, e2e, github-actions, jenkins, mergeable, test, travis-ci, woodpecker.

Note: A project that fulfills this criterion with other tools may still receive
a low score on this test. There are many ways to implement CI testing, and it is
Expand Down
2 changes: 1 addition & 1 deletion probes/testsRunInCI/impl.go
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ func isTest(s string) bool {
for _, pattern := range []string{
"appveyor", "buildkite", "circleci", "e2e", "github-actions", "jenkins",
"mergeable", "packit-as-a-service", "semaphoreci", "test", "travis-ci",
"flutter-dashboard", "Cirrus CI", "azure-pipelines",
"flutter-dashboard", "Cirrus CI", "azure-pipelines", "ci/woodpecker",
} {
if strings.Contains(l, pattern) {
return true
Expand Down
7 changes: 7 additions & 0 deletions probes/testsRunInCI/impl_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -238,6 +238,13 @@ func Test_isTest(t *testing.T) {
},
want: false,
},
{
name: "woodpecker",
args: args{
s: "ci/woodpecker/pr/test-release",
},
want: true,
},
}
for _, tt := range tests {
tt := tt
Expand Down
Loading