4 ms·
So we recommend branch per fork, merge what you like. You have to change the branch on each fork individually currently and thats unlikely to change in the sho
by benswerd 6mo ago
So we recommend branch per fork, merge what you like.
You have to change the branch on each fork individually currently and thats unlikely to change in the short term due to the complexity of git internals, but its not that hard to do yourself `git checkout -b fork-{whateverDiscriminator}`
- chrisweekly 6mo agoHave you considered git worktree?
- benswerd 6mo agoGreat for simple things, but git worktrees don't work when you have to fork processes like postgres/complex apps.
- ghm2199 6mo agoFor postgres there are pg containers, we use them in pytest fixtures for 1000's of unit-tests running concurrently. I imagine you could run them for integration test purposes too. What kind of testing would you run with these that can't be run with pg containers or not covered by conventional testing? I'll say this is still quite useful win for browser control usecases and also for debugging their crashes.