News for hackers. Stuff that matters.
Re:Parallel development without the headaches using Git work... by pprotas on Monday August 24, 2026 @01:02AM (#49415335)
On your last point, imagine worktree A talks to a database assuming some specific schema. If worktree B changes the schema (let’s day, we remove a column from a table), then worktree A can run into some errors.
Re:Parallel development without the headaches using Git work... by bdangubic on Monday August 24, 2026 @01:19AM (#49415438)
all schema changes should always be addition only
Re:Parallel development without the headaches using Git work... by pprotas on Monday August 24, 2026 @02:04AM (#49415720)
Maybe ideally, sure. In practice, in an org with multiple engineering teams: good luck enforcing that rule!
Re:Parallel development without the headaches using Git work... by bdangubic on Monday August 24, 2026 @08:36AM (#49418899)
no database user has drop rights - very easily enforced