From cfd52d9276a88f3cc8f4f4774acd0e54c8ea35c0 Mon Sep 17 00:00:00 2001 From: Eder Date: Sat, 11 Jul 2026 12:00:15 -0400 Subject: [PATCH] chore: keep agent instruction files out of the tracked tree Operator instruction files are maintained locally and no longer belong in the published tree. --- AGENTS.md | 41 ----------------------------------------- 1 file changed, 41 deletions(-) delete mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md deleted file mode 100644 index f3c553a4f19..00000000000 --- a/AGENTS.md +++ /dev/null @@ -1,41 +0,0 @@ -# Radarr Fork Agent Instructions - -These instructions apply to automated builders and reviewers working in this repository. - -## Session Startup - -- Work from a git worktree, not directly in the main checkout. -- Read this file at the start of each session before making changes. -- Check `git status --short --branch` before editing. -- Assume the worktree may contain user changes. Do not revert or clean them up unless the user explicitly asks. - -## Communication - -- Keep updates concise and factual. -- Act like an involved collaborator, not a passive executor. -- Push back when a request is risky, underspecified, or likely to create avoidable maintenance problems. -- Use role-based language such as `builder` or `reviewer` if you need to describe automation. -- Do not use emojis in commits, pull requests, issues, comments, or docs. -- Do not mention assistant product names in commits, pull requests, comments, or repo files. - -## Branch Workflow - -- This fork uses `develop` as the integration branch and `master` as the production branch. -- Keep upstream-sync or vendor-tracking work separate from Staros-specific release work. -- Do not assume upstream defaults are the same as this fork's release process. - -## Editing Standards - -- Match the existing .NET, frontend, and GitHub Actions patterns already in the repo. -- Keep changes narrow and avoid unrelated cleanup in the same commit. -- Use `rg` for search and `apply_patch` for manual edits. -- Update docs or workflow guidance when branch behavior, release flow, or automation expectations change. - -## Validation - -- Run the smallest useful check for the files you changed. -- For workflow-only changes, use focused review plus `git diff --check`. -- If you cannot run a validation step, state that clearly and call out the remaining risk. -## Git worktrees - -Worktree directory preference: create git worktrees under `~/worktrees//`, never inside this clone or `~/Documents/Repos.nosync/`. Merged/clean worktrees are auto-pruned weekly by `infra/scripts/prune-worktrees.sh` (launchd `dev.staros.worktree-janitor`).