Block a user
Codex ChatGPT auth should inject host access token via egress
Should require an explicit "forward_host_credentials" flag in the agent_provider manifest for this to happen, but otherwise looks good
didericis
deleted branch codex/codex-device-auth-runtime from didericis/bot-bottle
2026-05-29 02:48:18 -04:00
Stop injecting Codex API-key placeholder
didericis
pushed to codex/codex-device-auth-runtime at didericis/bot-bottle
2026-05-29 02:45:20 -04:00
didericis
pushed to codex/codex-device-auth-runtime at didericis/bot-bottle
2026-05-29 02:40:01 -04:00
didericis
created branch codex/codex-device-auth-runtime in didericis/bot-bottle
2026-05-29 02:40:01 -04:00
didericis
deleted branch prd-0028-git-gate-new-branch-scan from didericis/bot-bottle
2026-05-29 02:29:46 -04:00
didericis
pushed to prd-0028-git-gate-new-branch-scan at didericis/bot-bottle
2026-05-29 02:28:02 -04:00
didericis
pushed to prd-0028-git-gate-new-branch-scan at didericis/bot-bottle
2026-05-29 01:59:24 -04:00
didericis
pushed to prd-0028-git-gate-new-branch-scan at didericis/bot-bottle
2026-05-29 01:52:12 -04:00
didericis
created branch prd-0028-git-gate-new-branch-scan in didericis/bot-bottle
2026-05-29 01:52:11 -04:00
git-gate rejects all new-branch pushes: pre-receive scans full history and trips on test-fixture secrets
Why does gitleaks default to scanning all? Is there a potential for pushing to the upstream if we exclude refs already on the gate? I want to ensure change doesn't introduce a security issue.
git-gate rejects all new-branch pushes: pre-receive scans full history and trips on test-fixture secrets