You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cca48ad
Browse filesBrowse the repository at this point in the historyBrowse files
docs(devlog): third root cause, and this one is not the infrastructure's fault
My second explanation was also wrong. Dev is not scanned on push - its last
analysis is from 8/15, default setup runs weekly, and 0be660a is not an
ancestor of that commit, so the code was never in a dev scan. Dev's 84 alerts
are stale rather than current, which is the opposite of what I said they showed.
The real answer: github-advanced-security posted the finding as an inline review
comment on #1959 at 02:38:08Z, and #1963 promoted at 02:55:04Z. It sat in the
review thread of a promotion PR for seventeen minutes - while I was editing that
same PR's description. Not a coverage gap. I did not read the review comments on
a PR I was actively rewriting.
Three explanations for one mistake. The first two blamed infrastructure; the
third is true and the least comfortable, which is roughly how that tends to go.
0 commit comments