search

github / gh-valet

Valet helps facilitate the migration of Azure DevOps, CircleCI, GitLab CI, Jenkins, and Travis CI pipelines to GitHub Actions.
MIT License
510 stars 35 forks source link

Allow for user input to control which repositories to include in a cci audit #74

Closed ethanis closed 2 years ago

ethanis commented 2 years ago

What's changing?

This is adding a --include-from option for CircleCI audits for users to control exactly which repositories to include in an audit. This is to help scenarios where customers have a large GitHub org (>5k repos) where only a portion are configured with CircleCI. By using this option, customers can mitigate any potential API limit concerns with running an audit.

How's this tested?

repositories.txt

circle-yaml-aliases-example
circle-ci-ruby-example
$ dotnet run --project src/Valet/Valet.csproj -- audit circle-ci -o tmp --include-from repositories.txt --circle-ci-organization valet-testing-unit

cc/ github/valet#4539

github-actions[bot] commented 2 years ago

Unit Test Results

35 tests  ±0   35 :heavy_check_mark: ±0   0s :stopwatch: ±0s   1 suites ±0     0 :zzz: ±0    1 files   ±0     0 :x: ±0 

Results for commit d145df44. ± Comparison against base commit a39bdf32.