GitHub Desktop 3.6 adds worktrees and deeper Copilot integration. This engineering guide covers rollout policy, branch isolation, and review controls.
What GitHub Desktop 3.6 Changes for Engineering Teams
GitHub Desktop 3.6 brings worktrees into the desktop client and deepens Copilot integration. For engineering orgs, that is not just a UI upgrade. Worktrees let developers check out multiple branches at once in separate directories, which cuts context-switching cost and makes parallel review, hotfix, and feature work safer. Copilot living closer to the commit and PR flow changes how drafts are written, how diffs are explained, and how junior contributors get unstuck. The rollout problem is not feature discovery. It is policy: when worktrees are allowed, how isolation is enforced, and which review controls stay human-owned.
Treat the release as a process change. Desktop convenience can quietly bypass rules that already exist in CLI workflows, shared checkouts, and branch protection. A short rollout guide keeps the gains without letting local convenience become shared-main risk.
Rollout Policy Before You Flip the Switch
Start with a written policy, not a group chat announcement. Define who can use worktrees first, which repos are in scope, and what “done” means for a pilot. Prefer a small cohort on non-critical repos, then expand once the team can answer three questions: How do we create and name worktrees? How do we clean them up? How do we avoid two worktrees editing the same logical change?
- Require a single primary checkout per repo for shared automation and deploy scripts; worktrees are for human parallel work, not for every CI path.
- Ban force-push and direct commits to protected branches from any worktree path; protection rules apply to the remote, not the folder on disk.
- Document max open worktrees per engineer and a cleanup cadence so disk and stale branches do not pile up.
- Gate Copilot-assisted commits with the same review rules as hand-written ones; suggestions are drafts, not approvals.
Publish the policy in the same place as branch standards and link it from onboarding. If Desktop makes isolation easy, the policy must make misuse hard to do by accident.
Branch Isolation With Worktrees
Worktrees shine when the branch model is already clear. One worktree maps to one branch purpose: feature, review, hotfix, or spike. Do not share a worktree across unrelated tasks. Name directories after the branch or ticket so status is visible without opening the app. Keep long-lived worktrees rare; prefer short-lived paths that die when the PR merges.
Isolation fails when people treat worktrees as free clones of the same branch. Two directories on the same branch invite duplicate edits and confusing push history. Isolation also fails when local tooling assumes a single working tree: path-hardcoded scripts, secret files outside the repo, or language servers that cache the wrong root. Update local docs so “clone the repo” becomes “open the primary checkout or an approved worktree,” and make sure IDE and linter configs resolve relative to the worktree root, not a sibling path.
Review Controls When Copilot Is Closer to the Diff
Deeper Copilot integration can speed drafts, commit messages, and explanations of changes. Review controls must keep ownership explicit. Authors remain responsible for correctness, security, and whether the change matches the ticket. Reviewers should reject “AI said it was fine” as a rationale. Require that generated text in PRs is edited for accuracy, that secrets never land in suggested snippets, and that tests cover the behavior the model claimed to implement.
Operationally, keep mandatory reviews, status checks, and CODEOWNERS paths unchanged. Use Desktop’s convenience for navigation and draft quality, not for skipping checks. For high-risk areas—auth, billing, data migrations—add an extra human pass even when the summary looks clean. Train the team to treat Copilot output as a junior pair: useful for structure and wording, never authoritative on architecture or threat models. When the pilot ends, keep only the practices that reduced merge pain without weakening review. Worktrees and Copilot are tools for throughput; branch isolation and review policy are what keep that throughput safe.