Git-gate clean step #105
No Assignees
didericis-claude
didericis-claude
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: didericis/bot-bottle#105
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When git-gate clones, sometimes there's history in a repo which trips the wire for secrets. This interferes with pushes (and should possibly trigger history cleanup as well). We need some kind of flow to surface these issues and remediate them. Probably want it to happen in the dashboard AFTER git-gate detects an error. So flow should probably be:
git-gate action -> dashboard message -> user action -> sidecar refresh
I think this might be outdated: we are no longer parsing all the commits when we push through git-gate. Evaluate whether or not to close the issue.
Agree with closing. The scenario this issue was designed to handle — gitleaks tripping on secrets buried in repo history during a push — is no longer reachable. Issue #106 (closed 2026-05-29) scoped the pre-receive hook scan to incoming commits only (
--log-opts="$new --not --all"), so historical fixtures never enter the scan path.The remediation flow proposed here (git-gate error → dashboard message → user cleanup → sidecar refresh) was only valuable as long as full-history scanning could block a push. Since it can't, there's nothing to surface or remediate. Recommend closing as obsolete.