This week’s Copilot Workspace updates are focused on improvements to navigation and file management. As ever, drop your feedback into this discussion.
Simpler file tree navigation
When folders don’t have any direct file children but only have other folders as children, we now combine those into one folder to reduce the amount of nesting in the file tree.
In addition, when you open the file tree and have generated files, we now show Changed files as the default viewing mode.
Delete a file from the actions menu
By clicking on the ellipses in a file, you’re now able to delete a file directly from the actions menu of Copilot Workspace.
Opening files now opens them in an ephemeral tab
When you click a file in the tree, a new ephemeral tab is opened. When you double-click a file in the tree, it opens as a new regular tab. This aligns with the experience of most other IDEs and keeps your open tab list to just the ones you need.
Forwarded ports are easier to access
Now, when a command action uses port forwarding, a globe icon is added next to the command row, allowing you to view a live preview of the running port.
Improved screen layout in pull requests for smaller devices
Now, when working on smaller screens, the commit panel and suggestions pane will close as necessary, to better fit within your screen.
We want to hear from you
Please drop any and all feedback in our GitHub Discussion. We appreciate any and all feedback you have!
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
On March 31, 2025, GitHub Copilot Extensions will require an updated header format for agent requests. Both updated and previous versions of the request headers will be supported until then. These headers denote requests that come from GitHub and enable your extension to communicate with GitHub.
Previous headers, to be deprecated on March 31, 2025:
– Github-Public-Key-Identifier
– Github-Public-Key-Signature
Please update your relevant checks to the correct headers by March 31, 2025 for a consistent experience and to avoid breaking changes. To learn more, visit this page.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
Now in public preview, Linux arm64 hosted runners are available for free in public repositories. Following the release of arm64 larger hosted runners in June, this offering now extends to the open source-community. Powered by the Cobalt 100-based processors, these 4 vCPU runners can deliver up to a 40% performance boost compared to Microsoft Azure’s previous generation of Arm-based VMs, providing a power-efficient compute layer for your workloads. Arm-native developers can now build, test and deploy entirely within the arm64 architecture without the need for virtualization on your Actions runs.
How to use the runners
To leverage the arm64 hosted runners, add the following labels in your public repository workflow runs:
– ubuntu-24.04-arm
– ubuntu-22.04-arm
Please note that these labels will not work in private repositories, and the workflow will fail if added. All runs in public repositories will adhere to our standard runners usage limits, with maximum concurrencies based on your plan type. While the arm64 runners are in public preview, you may experience longer queue times during peak usage hours.
Images
In partnership with Arm, GitHub provides the Ubuntu VM images for these runners, helping customers with a seamless start to building on Arm. To view the list of installed software, give feedback, or report issues with the image, visit the partner-runner-images repository.
Get started today!
To get started, simply add one of the new labels to theruns-on syntax in your public Actions workflow file. For more information on arm64 runners and how to use them, see our documentation and join the conversation in the community discussion.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
