GitHub Desktop 3.6 makes Git workflows easier to manage

GitHub Desktop 3.6 is now available with worktree support and deeper GitHub Copilot integration. Published on June 26, 2026, the release brings Copilot-powered commit authoring, AI-assisted merge conflict resolution, model selection, bring your own key support, and a new way to work across multiple branches without constantly stashing or switching context.

{getToc} $title={Table of Contents}

GitHub Desktop 3.6 makes Git workflows easier to manage

GitHub Desktop 3.6 focuses on the Git moments that often interrupt everyday development work. Commit messages, merge conflicts, and switching between branches are not always the most visible parts of a web project, but they can slow down frontend teams, template creators, and small site maintainers when the workflow becomes messy.

The update brings more of that work into GitHub Desktop itself. Instead of depending only on manual Git commands, extra clones, repeated branch switching, or separate AI sessions, developers can use Desktop as a more guided place to write commits, resolve conflicts, and work across branches in parallel.

{getCard} $type={post} $title={More useful reading}

Worktrees help teams work across branches in parallel

One of the key additions in GitHub Desktop 3.6 is support for Git worktrees. This lets developers work across multiple branches at the same time without repeatedly stashing changes, switching branches, or cloning the same repository again.

For web design and frontend projects, this can be useful when a team needs to keep a main layout task open while also checking a hotfix, reviewing a small CSS change, or testing an experimental component. It can also fit better with coding agent workflows, where separate worktrees are often used to keep parallel sessions isolated from each other.

Copilot commit authoring gets more repository context

GitHub Desktop's commit message generation is also more customizable. The feature can pick up custom instructions from .github/copilot-instructions.md and AGENTS.md files, and it can follow commit metadata rules defined for the repository.

This matters because commit messages are part of project quality. A template repository, design system, plugin, or frontend app can become hard to maintain when commit history is inconsistent. Better commit authoring can help teams keep messages closer to their standards without requiring every contributor to remember every rule manually.

Merge conflicts can now get AI-assisted explanations

GitHub Desktop 3.6 also adds Copilot support for merge conflict resolution. When a conflict appears, Desktop can help explain the conflicting changes and suggest a resolution that the developer can review, accept, or edit before finishing the merge.

For frontend teams, this can be especially useful when conflicts involve layout files, shared components, configuration files, stylesheets, or generated code. The important point is that Copilot can assist with the explanation and suggested resolution, but the developer still needs to review the final result before merging.

IMPORTANT: GitHub Desktop 3.6.0 is available for macOS and Windows. GitHub Desktop is free to download and use, but Copilot-powered features require access to GitHub Copilot. Automatic updates roll out progressively, or users can download the latest release manually.{alertWarning}

Daisuki's Take: What This Means for Web Designers

For web designers who work with repositories, GitHub Desktop 3.6 is useful because it reduces friction around the Git tasks that sit between design changes and published code. Worktrees can make it easier to test multiple branches, while Copilot support can help with commit messages and conflict explanations.

We think the most practical part for template creators is worktree support. When maintaining themes, landing pages, UI kits, or design systems, it is common to pause one change to fix another. Worktrees give that process a cleaner structure without requiring extra repository clones.

The takeaway is to use these features as workflow support, not as a substitute for review. Copilot can help explain conflicts and author commits, but designers and developers still need to check the final code, test the layout, review accessibility, and confirm that the branch is safe before merging.

{getCard} $type={custom} $title={What's New?} $info={Find more AI Web design news} $icon={}

Sources and Recommended Links

• GitHub Desktop 3.6: Worktrees and deeper Copilot integration | GitHub Changelog
• GitHub Desktop | GitHub Official Product Page