Automatically credit remediation developers and reviewers - #61
Automatically credit remediation developers and reviewers#61sethmlarson wants to merge 3 commits into
Conversation
| "cve_id": cve_id, | ||
| "collaborating_teams": [{"slug": team} for team in collaborating_teams], | ||
| "collaborating_users": [{"login": "octocat", "id": 1, "type": "User"}], | ||
| "private_fork": {"name": "repo-ghsa-xxxx-xxxx-xxxx", "owner": {"login": "owner"}}, |
There was a problem hiding this comment.
Won't we loose coverage?
There was a problem hiding this comment.
I removed this field to avoid needing to mock out the pull requests response for each test case that didn't process private_fork. All the test cases that use private_fork already set the value.
StanFromIreland
left a comment
StanFromIreland
left a comment
There was a problem hiding this comment.
Can you also please update the flow chart in the README for this, TiA!
| ) | ||
| except RequestFailed: | ||
| capture_exception() | ||
| raise RuntimeError("Request to list pull requests failed") from None |
There was a problem hiding this comment.
We don't have coverage for these cases (to ensure we don't leak any other output), but that can be a follow up.
| ) | ||
| except RequestFailed: | ||
| capture_exception() | ||
| raise RuntimeError("Request to list pull requests reviews failed") from None |
There was a problem hiding this comment.
We could continue processing the next advisory instead?
There was a problem hiding this comment.
Eh, I worry all this would do is spam up Sentry with multiple failures instead of one. I think we want to keep this as stop-on-failure.
2 participants
The bot can automatically credit people who participate in creating a patch or reviewing the patch privately. Does not override credits that already exist for an individual.