Skip to content

chore: apply repository keeper defaults - #2

Merged
benjamin-small merged 2 commits into
mainfrom
repository-keeper/issue-1
Jul 27, 2026
Merged

chore: apply repository keeper defaults#2
benjamin-small merged 2 commits into
mainfrom
repository-keeper/issue-1

Conversation

@benjamin-small-repository-keeper

Copy link
Copy Markdown
Contributor

Repository Keeper remediation

Applied 6 deterministic fix(es); 10 finding(s) require repository-specific direction.

Proposed defaults

  • .github/CODEOWNERS — Applied the configured deterministic template.
  • CONTRIBUTING.md — Applied the configured deterministic template.
  • SECURITY.md — Applied the configured deterministic template.
  • docs/releases.md — Applied the configured deterministic template.
  • AGENTS.md — Applied the configured deterministic template.
  • .github/workflows/ci.yml — Applied the configured deterministic template.

Still needs repository-specific direction

  • repository-topics — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • repository-homepage — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • delete-branch-on-merge — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • branch-protection — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • code-scanning — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • licensing-present — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • configuration-documented — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • content — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • coverage-documented — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.
  • test-scope-documented — No deterministic default is enabled; discuss the repository-specific fix in the issue or pull request.

Tracks #1. The review issue closes only after a clean audit.

This is a draft. Review the defaults, request changes here, and let the target repository's CI validate them before marking it ready.

@benjamin-small-repository-keeper benjamin-small-repository-keeper Bot added the repository-keeper Automated Repository Keeper remediation label Jul 27, 2026
@benjamin-small
benjamin-small marked this pull request as ready for review July 27, 2026 13:32
@benjamin-small
benjamin-small merged commit 8a1e356 into main Jul 27, 2026
2 checks passed
@benjamin-small
benjamin-small deleted the repository-keeper/issue-1 branch July 27, 2026 13:32
benjamin-small added a commit that referenced this pull request Aug 21, 2026
Follows up on the code-review callouts against #2:

- ci.yml: scope push trigger to main (was every branch), add Swatinem
  rust-cache to skip cold builds on every PR, add concurrency group so
  a fast repush cancels the in-flight run, add manual workflow_dispatch.
- Delete .github/CODEOWNERS. Single-contributor repo — the file only
  set up a future self-merge lockout if branch protection ever gets
  enabled with require-code-owner-review. Re-add if collaborators land.
- New .githooks/pre-commit that runs cargo fmt --all --check when Rust
  files are staged; documented one-time install in CONTRIBUTING.md.
- Private Vulnerability Reporting enabled on the repo via gh api, so
  the SECURITY.md link (github.com/.../security/advisories/new) no
  longer 404s.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

repository-keeper Automated Repository Keeper remediation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant