Skip to content

Repository Automation

Nick edited this page May 16, 2026 · 2 revisions

Repository Automation

Mimick uses a small, focused automation stack for repository hygiene and release safety.

Current Automation

  • Dependabot for Cargo and GitHub Actions updates
  • CODEOWNERS for default repository ownership
  • Cargo vendor guard for cargo-sources.json
  • Docs link checking for README, docs, and wiki pages
  • Release Drafter for a rolling draft release page
  • Dependabot auto-merge workflow for approved dependency PRs

Why It Exists

This repo ships a Flatpak build that depends on vendored Cargo metadata, maintains a manual changelog, and relies on workflow-driven releases. A few guardrails go a long way here.

Important Manual Settings

The important GitHub-side settings are now in place on main:

  1. Allow auto-merge
  2. required status checks: Format, Lint, and Test, Dependency Audit, and Verify cargo-sources.json
  3. 1 required approving review
  4. required code-owner review
  5. stale approvals are dismissed on new commits
  6. conversation resolution is required

Key Files

Clone this wiki locally