Ignore "excluded_repos.csv" for code scanning alerts of GitHub Enterprise Cloud #31
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.
Background
Hi 👋 . I just realized that enterprise-level code-scanning-alerts function generates
excluded_repos.csv
in an unexpected format (not CSV).I am wondering that the
excluded_repos.csv
part is intended forGitHub Enterprise Server
which requires multiple API calls per repository. But, it would not apply forGitHub Enterprise Cloud
which can get the entire list with a single API call.Changes
excluded_repos.csv
logic forwrite_enterprise_cloud_cs_list
function.