Mercurial Phases: Using Draft, Secret and Public to Guard Your Pushes
Mercurial phases label each changeset as draft, secret or public to prevent accidental publication and support safe history rewriting in team workflows.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Mercurial phases label each changeset as draft, secret or public to prevent accidental publication and support safe history rewriting in team workflows.
An architecture note describing TowerGit’s interactive rebase: requirements, minimal UI design, trust boundaries, pre‑start checks, failure modes, and factors that would push the design toward a server‑mediated model.
Stop guessing your Git history. Learn how to use Sourcetree's visual graph and hunk-based staging to maintain a clean, atomic commit history and automate Git Flow.
Subversion's svn:needs-lock property flips binary files into a lock-modify-unlock workflow, making the checkout discipline self-enforcing for unmergeable assets like .psd, .blend, or .xlsx files.
Learn how to use TortoiseGit’s Interactive Rebase from the Windows Explorer context menu to squash or edit commits, with a step‑by‑step example and safety tips.
Git worktrees let you check out multiple branches into separate directories sharing one .git folder. Run a long build in one worktree while fixing a bug in another—no stashing, no duplicate clones. Here's how to set them up, a worked example, and the trade-offs to watch for.
Enable Node-RED Projects to put your flows under Git version control: setup in settings.js, creating and cloning projects, commit/push workflows, and recovery from bad deploys.
Stop using git stash for urgent context switches. Learn how to use Git Worktree to maintain multiple simultaneous working directories linked to one repository.
Subversion's svn:externals property embeds external repositories at specific revisions. Use peg revisions (URL@REV) to freeze externals at known-good states, repository-relative URLs (^/path) for mirror portability, and understand the commit, authentication, and performance implications.