Skip to content

GitHub Desktop 3.4 – Reset to Commit and Accessibility Settings

GitHub Desktop 3.4 lets you reset back to a specific commit quickly with “Reset to Commit” and improves discoverability of key application controls.

Resetting to Commit

With Reset to Commit, it takes one click to set your local history back to your latest pushed commit, with all of the reverted changes landing back into your changes list. While similar to using the undo function, Reset to Commit allows for resetting more than one commit at a time. By adding a new way to modify your history, Reset to Commit fits right along side undoing, reverting, amending, squashing, reordering, and cherry-picking features.

GitHub and the Desktop team are committed to making GitHub Desktop a tool for all developers. With GitHub Desktop 3.4, links are underlined by default and checkmarks are used in the diff to indicate whether a line is selected to be committed. These changes are aimed to enhance discoverability, be keyboard-accessible, and be semantically marked up to enable interaction with assistive technologies.

For users who want to opt out of these changes, check out the new Accessibility settings pane to customize your experience.

Automatic updates will roll out progressively, or you can download the latest GitHub Desktop here.

We’re excited to introduce a wave of updates this May 🌟 in GitHub Copilot Enterprise!

Copilot Chat in has leveled up 🔋. It can now summarize and answer questions about your repositories, releases, commits and more.

  • Learn about repositories: Copilot can answer questions about a repository or compare repositories based on its owner, description, stars & forks count, and various timestamps. To learn more, see “Asking exploratory questions about a repository” in the GitHub docs.
  • Try it yourself: Navigate to a repository on, and ask Copilot to Tell me about this repo
  • Ask about releases: Copilot can now tell you about a release or retrieve the most recent release in a repository. Ask Copilot to summarize the latest release from your favorite open source projects and use Copilot to dig into issues or changes tied to the release notes. To learn more, see “Asking exploratory questions about a repository” in the GitHub docs.

  • Try it yourself: Navigate to an open source repository on, and ask Copilot to Tell me about the latest release

  • Understand changes happening in your codebase: Copilot can now list changes (commits) related to a pull request and dig into specific commits if you need to understand a change in detail. To learn more, see “Asking a question about a specific commit” in the GitHub docs.

  • Try it yourself: Navigate to a commit on, and ask Copilot to Summarize the changes in this commit

Don’t know where to begin? Copilot Chat on now makes suggestions when you open a new conversation based on where you are. Whether you’re summarizing issues, creating unit tests, or discovering what Copilot can do, Chat already knows your GitHub context and what you might be trying to achieve.

With these latest updates for Copilot Enterprise, it’s now easier for you to get up to speed on your repos, their releases and latest changes faster and more seamlessly. You can learn more in our docs.

See more

GitHub secret scanning lets you know if your secret is active or inactive with partner validity checks. These checks are run on an ongoing basis for supported providers for any repositories that have enabled the validity check feature.

Starting today, secret validity will now be reflected in an alert’s timeline, alongside the existing resolution and bypass events. Changes to a secret’s validity will continue to be included in an organization’s audit log.

Sign up for a 60 minute feedback session on secret scanning and be compensated for your time.

Learn how to secure your repositories with secret scanning or become a secret scanning partner.

See more