Enterprise and organization administrators can now download a new GitHub Copilot activity report that provides enhanced visibility into user authentication and feature adoption. This report improves upon the legacy usage report with more timely and comprehensive data.

What’s new

The activity report introduces several improvements:

• Authentication tracking: The new last_authenticated_at field shows when users last authenticated with Copilot.
• Enhanced surface details: last_surface_used now provides specific IDE versions and github.com feature names.
• Improved data freshness: Reports refresh every 30 minutes instead of daily.
• Comprehensive coverage: Includes all generally available Copilot features across IDEs, github.com, the CLI, and mobile.

For more information on the contents of the report, see Metrics data properties for GitHub Copilot in our documentation.

Key benefits

• Better license management: Monitor actual Copilot usage with authentication timestamps.
• Adoption insights: Track usage of Copilot.
• Timely data: Updated on an interval of up to 30 minutes.
• 90-day retention: Historical data is retained for 90 days.

Access locations

The activity report is available via CSV download on the settings pages on github.com to Enterprise and Organization admins by following the steps below:

• For Enterprise administrators, Your enterprise → Policies → Copilot → Access
• For organization owners, Your organization → Settings → Copilot → Access
• For Enterprise teams, Billing & Licensing → Licensing → Manage Seats

Important timeline

The legacy usage report will be sunset over a 90-day period, ending October 23, 2025. We recommend transitioning to the new activity report to ensure uninterrupted access to usage insights.

For more information, see “Managing Copilot access” in our documentation.

The post New GitHub Copilot activity report with enhanced authentication and usage insights appeared first on The GitHub Blog.

We’re streamlining and enhancing Copilot code review! Upcoming features include moving from coding guidelines to copilot-instructions.md, making the Request pull request review from Copilot checkbox easier to find, and introducing a dedicated Copilot code review policy for more targeted organizational control. Let’s get started! 🚀

Deprecating coding guidelines in favor of copilot-instructions.md

We’re retiring coding guidelines (previously in private preview for Copilot Enterprise) and standardizing all Copilot customization in the new copilot-instructions.md file, which will be generally available for all customers on August 1, 2025. The coding guidelines playground will be deprecated the same day, and coding guidelines will be fully deprecated on September 1, 2025. Any existing guidelines you have created will continue to work until the full deprecation on September 1, 2025.

Automatic Copilot code review checkbox: Easier to find, easier to use ✅

The Request pull request review from Copilot checkbox in your repository rules, found in your repository’s settings, is moving out of the “Require pull request for merging” option and becoming a standalone, easily accessible option on August 6, 2025. This update requires no action for UI users-your existing selections will be migrated on your behalf. If you use the current API endpoint, plan to migrate before it is deprecated in September 2025. Stay tuned for future updates, including the option to automatically run Copilot code review on new pushes and drafts!

Introducing a dedicated enterprise and organizational policy for Copilot code review

Copilot code review is getting its own distinct policy, separate from Copilot in github.com, and rolling out soon! Organizations with the current policy will see Copilot code review automatically match their existing settings. In addition, enterprises can soon globally disable Copilot code review for all users, including Free, Pro, and Pro+ licenses. This brings clearer, more granular control, without disrupting current usage.

Questions or feedback?

For questions about any of these updates, join the conversation in our GitHub Community discussion. We’d love to hear your thoughts!
We’re excited to keep improving Copilot code reviews for everyone!

The post Upcoming deprecations and changes to Copilot code review appeared first on The GitHub Blog.

We’ve made numerous improvements to the new pull request “Files changed” page that launched as a public preview in June. This new page will eventually replace the existing page and provide a more accessible, better performing, and more usable experience for reviewing pull requests of all sizes.

💬 Comment on files

You can now comment on individual files, including binary, deleted, and renamed files, just like you could in the classic page. See the following video for an example of this in action:

🚀 Performance

Improving the performance of the new page continues to be a priority, and we shipped fixes to improve the responsiveness of user interactions (as measured by INP).

• Reduced unnecessary re-renders after page load, when dragging to select lines, and other diff interactions.
• Improved responsiveness when clicking the + (add comment) button.
• Fixed a Chrome-specific issue causing high CPU and memory utilization.

🔧 Other improvements

We continue to make fixes and add enhancements based on your feedback including:

• Fixed: Expanding a diff hunk previously failed for files with special characters in their name.
• Fixed: Incorrect diff content previously appeared when viewing certain large pull requests and filtered to a range of commits.
• Fixed: Previously some diffs would appear stuck as loading.
• Fixed: The file tree previously disappeared at specific screen widths.
• Improved: Resolve comment is now a full size button (not just an icon).
• Added: The “processing updates” message now appears when changes pushed to the pull request branch are not ready to be shown on the page.

🔄 Known issues

There are still feature parity gaps that exist between the new and existing pages that we are working to address. The following features are not yet available:

• Rich diff previews for image (SVGs, PNGs, etc) and markdown files
• Reviewing a single commit
• Code scanning alerts (and the ability to dismiss the alerts)
• Keyboard shortcuts, including to hide annotations

The new page is currently limited to only showing the first 300 files of the pull request. If you need to view larger pull requests, you can easily switch over to the classic page.

We are also tracking bugs across all parts of the new page, including related to filtering, diff rendering, the new comments side panel, the new review submission panel, and more. Visit the feedback discussion for an up-to-date list of known issues.

📣 Feedback

Your feedback is super important to us! To report problems, ask questions, see the latest news, and more, visit the feedback discussion.

If you haven’t tried the improved experience yet, click the Try the new experience link at the top of the existing “Files changed” page.

The post Pull request “Files changed” public preview – July 17 updates appeared first on The GitHub Blog.

As of July 17, 2025 usage of https://models.inference.ai.azure.com for GitHub Models inference and embeddings is officially deprecated.

This change follows the launch of the GitHub Models API on May 15, 2025, which offers a fully supported, billable, and enterprise-ready way to access GitHub-hosted models through https://models.github.ai.

If you’re currently using https://models.inference.ai.azure.com, requests will temporarily continue to function, but we will remove support on October 17, 2025. After that date, GitHub Models usage must go through https://models.github.ai to receive valid responses.

To ensure access to the latest features, authentication, and accurate billing, all users should transition to the new GitHub Models API as soon as possible.

Learn more about GitHub Models, our new GitHub Models REST API, or join the community discussion to help guide our roadmap!

The post Deprecation of Azure endpoint for GitHub Models appeared first on The GitHub Blog.

Stay in flow with the latest updates to GitHub Issues and Projects. You can now duplicate issues across repositories and start new issues from anywhere in the GitHub UI. These updates help you streamline your workflow and keep projects moving.

Duplicate an issue to any repository

You can now quickly duplicate any issue 🎉 with the new Duplicate issue option, which appears at the bottom of the right issue sidebar.

Here’s how it works:

• Click Duplicate issue to open a new issue form prefilled with the original issue’s content. This includes the title, description, assignees, labels, type, projects, and milestone.
• Change the destination repository before creating the duplicated issue, making it easy to copy issues across repositories.
• Edit any details before creating the new issue to fit your workflow.

This feature helps you:

• Reuse issue formats or recurring tasks without manual copy-paste.
• Split large issues into smaller, actionable items.
• Create similar issues across multiple repositories.

Let us know what you think and share your feedback in the discussion within the GitHub Community.

Create issues from anywhere in the GitHub UI

You can now create a new issue from anywhere while you’re using GitHub. Just use the New issue button in the header to quickly open the issue creation modal no matter which page you’re on. This helps you capture ideas or tasks as they come up, without interrupting your workflow.

API support for issues advanced search

Following the opt-in support for advanced issue searches using the API, all issue queries will use advanced search by default on September 4, 2025. This means that after this date:

• You will no longer need to use the advanced_search parameter for the REST API.
• The ISSUE GraphQL type will support advanced search.

Additional improvements

• In a project, issues are now ordered alphabetically when sorting or slicing by the Parent issue field.
• Select Reorder fields from the custom fields ... menu on the projects setting page to determine the order of custom fields on a project item and in field lists.
• Close issues as duplicates programatically via the REST API.
• GraphQL field Issue.timeline has been removed. You can use Issue.timelineItems instead. Please see the GraphQL API documentation for details.

Tell us what you think!

Join the conversation within GitHub Community, or select Give feedback from the project ... menu to share your feedback!

See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in our GitHub Issues documentation.

The post Duplicate issues, create from anywhere, and more appeared first on The GitHub Blog.

The GitHub macOS hosted runner fleet is being upgraded to M2 Pro-powered machines on our largest runners. Starting today the macOS XLarge runner sku now utilizes a 5 vCPU M2 Pro machine.

M2 Pro machines

Apple developers can take advantage of the more powerful machines using the latest versions of iOS and macOS. They can also benefit from increased performance by leveraging the on-chip GPU capabilities of the M2 processor. It can reduce build times by up to 15% compared to the existing 6-core M1 runner. The M2 macOS runner comes with GPU hardware acceleration enabled by default. Workloads are transferred from the CPU to the GPU for improved performance and efficiency. The runner is equipped with a 5-core CPU, 8-core GPU, 14 GB of RAM, and 14 GB of storage.

How to use the runners

To try the new M2 macOS larger runner, update the runs-on: key in your workflow YAML file to target one of the following labels:

• macos-latest-xlarge
• macos-15-xlarge
• macos-14-xlarge
• macos-13-xlarge

The 6-core M1 macOS larger runner is no longer available.

Pricing for M2 runners

There is no price change from the existing XLarge runner sku with today’s launch. Pricing for these runners is $0.16/min.

There is no sign-up required for the public preview and the runner is immediately available to all developers, teams, and enterprises. For more information on the M2 runners please see our larger runner documentation. Join the discussion within GitHub Community.

The post GitHub Actions now offers M2 Pro-powered hosted runners in public preview appeared first on The GitHub Blog.

GitHub Copilot agent mode for JetBrains, Eclipse, and Xcode is now generally available! You can enable GitHub Copilot with any GitHub account and experience the autonomous coding experience today.

✨ What’s new

Agent mode is now generally available for JetBrains, Eclipse, and Xcode users. Unlike traditional chat or multi-file edits, agent mode is designed to autonomously translate your intent into code by taking action across your project. With a simple prompt, agent mode can analyze your codebase, break down your request into actionable steps, and execute changes across multiple files or generate new ones as needed to achieve your goal.

In these IDEs, agent mode can also suggest terminal commands or tool invocations and prompt you to run them, streamlining tasks like building your project or installing dependencies. If errors occur during execution, agent mode analyzes run-time issues and applies self-healing techniques to resolve them automatically.

With agent mode in JetBrains, Eclipse, and Xcode, Copilot becomes an active coding partner by handling multi-step tasks, proposing and applying edits, and ensuring your workflow stays smooth from start to finish.

🛠 Try it out

Get started with our official documentation:

• Agent mode for JetBrains
• Agent mode for Eclipse
• Agent mode for Xcode

💬 Share your feedback

Your feedback drives improvements. Let us know what you think using the in-product feedback option or share your thoughts in the following channels:

• GitHub Copilot for JetBrains feedback
• GitHub Copilot for Eclipse feedback
• GitHub Copilot for Xcode feedback

The post Agent mode for JetBrains, Eclipse, and Xcode is now generally available appeared first on The GitHub Blog.

Copilot on github.com now supports improvements to the experiences you already know and love.

Creating issues with Copilot supports issue forms

When creating issues with Copilot, it can now select from your repository’s issue forms and ensure all required fields are completed before submission. Copilot recommendations templates and forms, helping you to maintain clean project documentation and to save you valuable time.

Receive more results when asking about GitHub data

We’ve supercharged your GitHub data retrieval with a 10x boost. Now you can get up to 100 results per query instead of just 10 for issues, pull requests, commits, and more. This means more comprehensive analysis for larger sets of data.

This improvement is perfect for sprint planning, code review insights, team productivity tracking, and getting the complete picture of your project’s health without missing critical details. Don’t forget to attach a repository to your query to get better results.

Spaces supports file uploads and images

You can now upload text and image files from your local environment directly to a space. Upload documentation, video call transcripts, screenshots of a mock-up, debug logs, data exports, and more. This capability currently supports textual content (e.g., .txt, .log, .json, .cpp) as well as standard image formats such as .png, .jpg, and .tiff—rich text formats like .pdf and .docx are not yet supported.

Your feedback drives our improvements! Let us know what you think using the in-product feedback option or share your thoughts in the GitHub Community.

The post Support for issue forms in chat and file uploads in spaces appeared first on The GitHub Blog.

GitHub Copilot coding agent, currently in public preview, has limited internet access by default to help protect your data and mitigate security risks.

Today, we’re releasing an updated experience that allows you to more easily control Copilot’s internet access. From the “Coding agent” settings page in your repository, you can now:

• Add custom hosts to the allow list.
• Opt out of GitHub’s recommended allow list for a more locked-down configuration.
• Choose to entirely disable the firewall.

If the agent tries to make a request that your firewall blocks, Copilot will add a warning to your pull request.

Copilot coding agent is available to all paid Copilot plans. To learn more, see the firewall configuration documentation, or check out other coding agent features.

The post Configure internet access for Copilot coding agent appeared first on The GitHub Blog.

Starting August 6, 2025, the command palette feature preview will be deprecated and will no longer be available on GitHub. If you currently use the command palette, make sure to plan for this change.

We’re deprecating the command palette due to low usage. This allows us to put more resources into experiences that make a bigger impact for the community.

If you have feedback, let us know in GitHub Community discussions.

The post Upcoming deprecation of GitHub Command Palette feature preview appeared first on The GitHub Blog.