Skip to content

chore: ignore local agent artifacts#17

Open
ChunkyTortoise wants to merge 2 commits into
mainfrom
chore/maintenance-2026-05-26
Open

chore: ignore local agent artifacts#17
ChunkyTortoise wants to merge 2 commits into
mainfrom
chore/maintenance-2026-05-26

Conversation

@ChunkyTortoise
Copy link
Copy Markdown
Owner

Summary

  • Adds local agent/runtime artifacts to .gitignore.
  • Keeps generated maintenance residue out of future commits.

Verification

  • git diff --check -> passed

Notes

  • No deploys performed.
  • No package installs performed.

Suppress 16 false-positive findings from the Five-Gates adversarial
corpus (intentional fake JWT secrets and attack tokens, not real
credentials). Downstream users running gitleaks against this toolkit
will no longer trip on the bundled security-test inputs.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5289565aca

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .gitleaks.toml
Comment on lines +12 to +16
paths = [
'''evals/quality/tasks\.py''',
'''tests/adversarial/injection_corpus\.jsonl''',
'''tests/gates/test_gate_safety\.py''',
]
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Narrow the path allowlist to the fixture lines

Because this is a global Gitleaks path allowlist, every finding in these matched files is suppressed, not just the known fake JWT/test corpus values. In the scenario where a real API key or token is accidentally added later to evals/quality/tasks.py, tests/adversarial/injection_corpus.jsonl, or tests/gates/test_gate_safety.py, the scanner will stay silent even though SECURITY.md says secrets must never be hardcoded; prefer line/fingerprint-specific ignores or regexes for the intentional fixtures.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant