[jorl17]

Hi! Congratulations on building something new!

I'm going to look into it soon, but since you might be hanging around here, I'll ask: do I have a quick way of telling the system how to actually creating a worktree efficiently?

Here's my problem: I want to do manual testing for several things, especially frontend related ones. However, every worktree needs its own ports, and specific particularities (e.g. so docker volumes don't collide). `git config --worktree` is supposed to help with this (and I'll be looking at it pretty soon), but it seems very primitive.

Is there a way for me to tell Emdash: "Hey, when you create a new worktree, you need to run this script"?

Thanks in advance and, once again, congrats on building something new, clearly in the direction we are going.

[onecommit]

Yes! By default, every new task runs in its own worktree. In the .emdash.json config (or in the UI on your project page), you can specify setup, run, and teardown scripts -- pnpm install, pnpm run dev, etc.

We also inject convenience env vars into every task. For example, $EMDASH_PORT gives each task a unique port, so you can do PORT=$EMDASH_PORT pnpm run dev and never collide on dev servers.

More here https://docs.emdash.sh/project-config -- does that help?

[jorl17]

THANK YOU!!

This seems like just what I was looking for — amazing!!

I hope I have the time to test-run it over the coming days.

If this really ups my ante, I'll get the whole team using it at our studio. Looks promising!

[arnestrickmann]

Sounds amazing! Let us know if there are any issues or what we can do better!