Remove leaked GitHub PAT from .codex/config.toml + gitignore it#115
Merged
Conversation
Introduce a new set of agent skills for structured AI development, including: - CritterBids-specific best practices (dual evaluation, frontend slice discipline, SignalR client conventions). - OpenSpec CLI integration for `propose`, `explore`, `apply`, and `archive` workflows. Update `AGENTS.md` to document the OpenSpec workspace, update skill invocation guidance, and detail frontend architecture. Also configure Model Context Protocol (MCP) servers in `.codex/config.toml` to support these new agent capabilities.
Resolve IMessageBus from child scope instead of root provider to satisfy DI scope validator in Development environment. Add AsyncServiceScope field with disposal in both RelayHub and PostSaleFanOut test fixtures. Update Aspire packages to 13.4.6, WolverineFx to 6.14.0. Correct nuget.config package source mapping to route only JasperFx.AiSkills to private feed (all WolverineFx/Marten packages resolve from nuget.org).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
These are the two previously-unpushed local commits (
6dbe80c,9bec5e0), rewritten to strip a secret that GitHub Push Protection had blocked..codex/config.toml(the local Codex MCP config). The file is now untracked; the working copy stays on each developer's disk..codex/config.tomlto.gitignore, in the existing "AI Tool MCP Configuration Files (may contain GitHub PATs)" section alongside.vscode/mcp.jsonand.cursor/mcp.json— it had simply been missing from that list.Why
The original push of
mainwas rejected by GitHub Push Protection (GH013/GITHUB PUSH PROTECTION): a GitHub PAT was present at.codex/config.toml:47in commit6dbe80c. The secret never reachedorigin— it existed only in unpushed local commits.How it was done
History was rewritten onto this branch rather than pushed to
maindirectly (per the repo's branch-and-PR convention):origin/main(b6f0c8f)6dbe80cwith the secret file untracked + the.gitignoreentry folded into the same commit (ff61d58)9bec5e0unchanged (e4f3f52)mainreset back toorigin/mainAll code files preserved byte-for-byte (13→13 changed-file parity on the rewritten commit; only the config file was swapped for the gitignore line).
Follow-up (recommended)
The exposed token should be rotated at https://github.com/settings/tokens. Exposure was local-only (it never hit the remote), but the credential sat in plaintext in a commit object + terminal history, so regenerating it is the only way to fully retire it.