actions/cache-apt-pkgs-action
1
0
Fork 0
mirror of https://github.com/awalsh128/cache-apt-pkgs-action.git synced 2026-11-13 21:36:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add ts-apt boundary rules to AGENTS.md

Browse source 
APT and dpkg logic belongs in ts-apt; ts-apt changes are pushed before the action bumps its pin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
awalsh128 2026-11-06 09:51:27 -08:00 committed by Andrew Walsh
parent b22ee197c7
commit 7963e3ef89
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
AGENTS.md
View file

@ -9,6 +9,7 @@ You are an expert developer focused on TypeScript, Bash, DevOps, Git, and GitHub
3. `Section 2` for tests.
4. `Section 3` for CI/CD and release work.
5. `Section 4` for repo-specific paths and commands.
6. `Section 5` before touching APT, dpkg, or package-name logic.
## Instruction Efficiency
@ -72,6 +73,20 @@ You are an expert developer focused on TypeScript, Bash, DevOps, Git, and GitHub
- Use `scripts/dist/` for shell assets bundled with the npm package and exposed through `package.json` bin/files entries.
- Use `scripts/` as the home for repo-owned automation; do not refer to the old `dev_scripts/` layout.
## 5) ts-apt Boundary
- ts-apt owns APT and dpkg logic; its local clone is `../ts-apt`.
- MUST make changes in `../ts-apt` when they run `apt`, `apt-get`, `apt-cache`, `apt-fast`, `dpkg`, or `dpkg-query`.
- MUST make changes in `../ts-apt` when they parse APT or dpkg output or change `PackageName` behavior.
- NEVER call APT or dpkg binaries from `src/`; add a `PackageManager` method in ts-apt and call it.
- This repo owns cache keys, manifests, archives, action inputs, and action outputs.
- Follow `../ts-apt/AGENTS.md` when editing ts-apt.
- Add ts-apt unit tests for every new ts-apt method.
- Use `npm run dev:tsapt:link` to test against local ts-apt; run `npm run dev:tsapt:unlink` when finished.
- `package.json` pins ts-apt to a commit SHA; local ts-apt changes are not visible to CI.
- MUST push the ts-apt change first, then bump the ts-apt SHA pin in the same change that uses it.
- NEVER push action code that depends on an unpushed ts-apt change.
## Quick Commands
```bash