Matthew Bessette
13 lines
1.2 KiB
Markdown
13 lines
1.2 KiB
Markdown
# Personal instructions
|
|
|
|
## Where code lives
|
|
- "The code", "the repo", "the monorepo", or any general code question refers to `~/Projects/cleo-infinite`.
|
|
- Anything mentioning Retool refers to `~/Projects/cleo-retool`.
|
|
|
|
## Worktrees
|
|
- Never write or edit code in the main checkouts (`~/Projects/cleo-infinite`, `~/Projects/cleo-retool`). Work in a treehouse worktree under `~/.local/share/treehouse/<repo>-<hash>/<slot>/<repo>`. Check with `git rev-parse --show-toplevel` and `git worktree list`.
|
|
- If code changes are needed and the current directory is not a treehouse worktree, start one yourself without asking first, then continue there. Read-only investigation can stay where it is.
|
|
- Treehouse is a zsh alias for `nix run github:kunchenguid/treehouse --`, so it is not on PATH in non-interactive shells. Run the full `nix run` form, and run it with `--help` first rather than guessing subcommands or flags.
|
|
- Branch names follow the repo's own rules (cleo-infinite: `<JIRA-KEY>-short_slug` from latest `origin/main`). Take the Jira key from the user or the current branch. If there isn't one, ask. Never invent a key.
|
|
- A pool slot sitting on a detached HEAD is not necessarily free. Don't reuse a slot that has uncommitted changes or that another session may be using.
|