Skip to content

docs: plan pnpm migration #812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danshapiro merged 1 commit into from
Sep 19, 2026
+516 −0
Merged

docs: plan pnpm migration #812

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@ Freshell is a self-hosted, browser-accessible terminal multiplexer and session o
- We fix the system over the symptom.

## Repo Rules

Proposed package-manager migration: [pnpm migration plan](docs/plans/2026-09-19-pnpm-migration.md). This is a planning artifact, not a change to the current npm workflow.

- Always work in a worktree (in \.worktrees\)
- Pull before starting major work: `git fetch origin` and bring local `main` to `origin/main` (fast-forward) so new work always bases on the latest merged state.
- Before creating a new worktree, ensure the repo-supported test suite is green on the intended base. If the suite is not green, pause before creating the worktree and notify the user with the failing command and failure summary.
Expand Down
Loading
Loading