Files
computer-playbook/docs/contributing/tools/github/repository.md
T
kevinveenbirkenbachandClaude Sonnet 4.6 5cebe3ea63 feat(ci): add CI_CANCEL_IN_PROGRESS variable and restructure branch docs
- Use vars.CI_CANCEL_IN_PROGRESS in entry-push-latest.yml so cancellation
  can be disabled per-repo without changing workflow code
- Move docs/contributing/tools/github/branch.md into branch/ subdirectory
  as security.md; add configuration.md for CI repository variables and
  README.md as directory index
- Fix all cross-references in SECURITY.md, pipeline.md, branch.md,
  pull-request.md, workflow.md, and repository.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-13 22:18:02 +02:00

1.3 KiB

Repository Settings 🔧

See also branch.md for branch protection rules.

Dependency Management 📦

Dependency Graph ❌

👉 Contributors may not have access to full dependency insights

Dependabot Alerts ❌

👉 Vulnerabilities may go unnoticed

Dependabot Security Updates ❌

👉 Contributors MUST update dependencies manually

Dependabot Version Updates ❌

👉 No automatic upgrade PRs


Code Scanning (Global) 🔬

CodeQL ✅

👉 Security issues may be detected automatically

Copilot Autofix ✅

👉 Suggested fixes may appear


Secret Protection 🔐

For GHCR authentication configuration see authentication.md.

Secret Scanning ❌

👉 Secrets may accidentally be committed

Push Protection ❌

👉 Commits with secrets are NOT blocked


Summary for Contributors 📋

Once enabled, you MUST:

  • Create a PR (no direct push)
  • Get 2 approvals
  • Get CODEOWNER approval (if applicable)
  • Resolve all comments
  • Re-approve after changes
  • Keep branch up-to-date
  • Use signed commits
  • Pass code scanning & quality checks

You MUST NOT:

  • Push directly to main
  • Force push
  • Merge without approvals

You MAY:

  • Create branches freely
  • Use merge commits

All rules above are currently enforced on main.