Add BranchProtectionConfigurationEvent and SecretScanningAlertLocationEvent#3332
Add BranchProtectionConfigurationEvent and SecretScanningAlertLocationEvent#3332gmlewis merged 3 commits intogoogle:masterfrom
Conversation
…ning_alert_location
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3332 +/- ##
==========================================
- Coverage 97.72% 93.01% -4.71%
==========================================
Files 153 172 +19
Lines 13390 14848 +1458
==========================================
+ Hits 13085 13811 +726
- Misses 215 944 +729
- Partials 90 93 +3 ☔ View full report in Codecov by Sentry. |
|
Please fix the unit tests locally by running the commands in step 4 in CONTRIBUTING.md and then push (not force-push) the changes to this PR. |
@gmlewis this seems like an intermittent failure unrelated to the changes in this PR. Unable to reproduce it locally. Can we re-run the workflow? |
| "code_scanning_default_setup": "enabled" | ||
| } | ||
| }`) | ||
| w.WriteHeader(http.StatusOK) |
There was a problem hiding this comment.
The changes to this file seem wrong to me.
I think you can revert the changes to this file.
There was a problem hiding this comment.
This was a warning which I fixed.
Per https://pkg.go.dev/net/http
If WriteHeader is not called explicitly, the first call to Write
will trigger an implicit WriteHeader(http.StatusOK).
So I think we should either keep this change or explicitly call w.WriteHeader(http.StatusOK) before we write to w. Any thoughts?
There was a problem hiding this comment.
Oh, interesting, so this is unrelated to this PR. OK. I'm fine to keep the change. Thanks.
|
Thank you, @tomfeigin ! |
No description provided.