Skip to content

GitHub Secret Scanning improvements #5638

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

Merged
merged 7 commits into from
Dec 13, 2022
Merged

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Dec 13, 2022

This PR builds on top of #5495 and improves the code a little bit more. See the individual commit messages for more details.

The comparison is essentially the same, but slightly more straight forward to understand.
…` function

We shouldn't panic if the network call fails, instead we can forward the error and return a 500 response.
@Turbo87 Turbo87 added C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear A-backend ⚙️ labels Dec 13, 2022
@Turbo87 Turbo87 marked this pull request as ready for review December 13, 2022 11:31
… function

The logic is essentially the same, but using `find()` and `let-else` to simplify the code.
…N parsing

We can use `from_slice()` instead to simplify the code
If GitHub reports a potential token we should treat false positives as legitimate cases instead of errors. Only real errors like failing to revoke a token should be considered errors.
@Turbo87 Turbo87 merged commit fb56426 into rust-lang:master Dec 13, 2022
@Turbo87 Turbo87 deleted the gh-secret-alerts branch December 13, 2022 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

1 participant