You can now specify a custom JSON schema as a response format, alongside the existing text and recently released general JSON option. When JSON schema is selected, an input box will allow you to define your desired schema format directly in the playground.
This enhancement provides more control if you’re working with models that require structured responses, helping to mitigate issues like models outputting unnecessary tokens. You can either specify a single object or an array of objects. Additionally, you can save this JSON schema as a preset so that you can use it again later.
JSON Schema structured outputs are currently only supported for the GPT 4o model, and specifically for the api-version: “2024-08-01-preview”.
GitHub Models is a catalog and playground of AI models to help you build AI features and products. You can start using models for free with just your GitHub PAT.
To support better content moderation, you can now disable comments on individual gists in the UI as well as with the APIs. Once commenting is disabled, existing comments on the gist will be hidden and no new comments can be posted.
You can now add a new file directly to the file tree, rather than having to modify the plan.
Error toggling
We’ve enabled an option to toggle errors on and off within your editor. This will allow you to hide errors when you’re not actively working on them.
Improved codespace creation
Now when you create a codespace, your codespace will be created in the region closest to you. This will improve the latency of your connection, providing a smoother experience while editing and using the terminal.
Copilot Workspace for pull requests
Accessibility improvements
Screen readers will now announce when suggestions are applied.
Bug fixes
Fixed a design regression where there was no border between the editor and the file.
Providing feedback
Please give 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 February 5th, 2025, Dependabot will end support for Python version 3.8, which has reached its end-of-life. If you continue to use Python version 3.8, there’s a risk that Dependabot will not create pull requests to update dependencies. To prevent this from happening, please update to a supported release of Python. As of January 2025, the latest supported release of Python is version 3.13. View Python’s official documentation for more information about supported releases.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
Starting January 6, 2025 GitHub-Hosted macOS runner images will be replacing Xcode 16.0 with Xcode 16.2. This change applies to both macOS-14 Intel and ARM64 based runner images. If you rely on Xcode 16.0, upgrade to Xcode 16.1 in order to maintain service continuity in your Actions workflows.
Our support policy for macOS-14 is:
– Xcode 15: All minor releases with the full platform tools suite.
– Xcode 16: Two minor releases (excluding visionOS tools), following a “last two” principle where the oldest version is replaced by the latest as updates are released. Beta versions are not included.
Copilot Workspace is a Copilot-native development environment designed to help you with everyday tasks, from idea to merge.
Starting from a GitHub Issue or natural language task, you can work with Copilot Workspace to iterate on solving your problem. Together, you can:
Brainstorm your ideas: Ask Copilot questions about how your codebase currently works, and explore ideas for how to solve your task.
Plan your changes: Leverage Copilot Workspace to generate a comprehensive plan for your code change, surfacing relevant code and describing the changes necessary in each file to achieve your goal.
Implement and validate: Let Copilot Workspace propose code changes that you can iterate on and refine in natural language or code. You can even build, run, and test the code directly within Copilot Workspace with a fully functional compute environment provided by GitHub Codespaces before creating a pull request.
Everything that GitHub Copilot Workspace proposes – from the plan to the code – is fully editable, allowing you to rapidly iterate until you’re confident in the change.
Sign up for the technical preview by logging into Copilot Workspace. Please note that Enterprise Managed Users are not eligible for the technical preview.
Organization administrators can enable members to use Copilot Workspace with repositories owned by their organization by approving the Copilot Workspace OAuth app for the organization. OAuth app restrictions are enabled by default when new organizations are created, so unless you’ve changed this setting, members of your organization will not have access to Copilot Workspace on organization-owned repositories by default. To enable Copilot Workspace for your organization’s repositories:
Workspace will now inform you when a file is too large to be displayed, and link you to view the file in the repo editor.
Copying the branch name
Now when selecting a branch, you’ll be able to copy the branch name to your clipboard. You’ll will see a check mark after successfully copying the branch name.
Improvements to the diff editor
The scrolling experience has been improved, allowing you to scroll through all your files at once instead of each file individually.
We’ve enabled collapsing regions outside the diff, and are showing 3 lines of context padding the diff.
We’ve enabled word wrapping within the editor.
Bug fixes
Empty files now display correctly
Fixed a bug during plan creation that was causing Copilot Workspace to crash
No longer does renaming the spec question include a scroll bar
Fixed an issue where renamed files did not update all references across the plan, tabs, and editor. Now when you rename a file you will see that name change reflected everywhere.
Copilot Workspace for PRs
New file path auto-populating
Adding new files will auto-populate the path, making it easier to add new files to your repository.
Individual file resets
You can now reset individual files, rather than having to reset the state of all changes.
Hiding trailing whitespace
We’ve enabled an option for you to hide whitespace when viewing a diff.
Add indication when suggestion cannot be applied
We now alert you when a suggestion can’t be applied.
Accessibility improvements
Accessibility continues to be core to the GitHub experience. Over the upcoming changelogs we’ll be highlighting improvements to our accessibility experience.
User operating system specific hints on keyboard shortcuts are enabled
A missing checkbox label on commit dialog has been added
Screen reader feedback on suggestions are now applied
Bug fixes
Copilot Workspace now informs users if a file is too large to be viewed
Changing files is enabled when focusing on a suggestion
Suggestions that would be applied to files you have removed are now deleted
Providing Feedback
Please give 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!
As a GitHub Enterprise Cloud organization owner, you and your designated users can now use API insights to visualize REST API activity for your entire organization or specific apps and users. This new feature helps you understand the sources of your REST API activity and manage against your primary rate limits—giving you visibility into the timeframe, apps, and API endpoints involved.
Who can access it
The API insights feature is available only at the organization level. By default, only organization owners can access it. However, organization owners can grant access to non-owners by creating a custom role at the organization level, assigning the permission named View organization API insights to the custom role, and then assigning the custom role to an organization member or team. See the documentation for managing organization custom roles.
Where to find it
The API insights feature is available to all GitHub Enterprise Cloud organizations. To access it on your organization home page, select Insights near the top of the page, and then select REST API on the left side of the page.
How to use it
Use the Period and Interval drop-downs to choose the range of time displayed in the chart and how granularly to display REST API requests on the chart. These drop-downs also set the time range for the “Total REST requests,” the “Primary-rate-limited requests,” and the Actors table below the chart.
The Actors table displays the GitHub Apps and users that made REST API requests in the current organization within the selected time period. Select a GitHub App to display its REST API activity and any primary rate-limiting. Select a user to display their personal REST API activity from personal access tokens (PATs) and OAuth apps acting on their behalf.
Refer to the documentation for API insights for more details about understanding your organization’s REST API activity and investigating primary rate-limiting.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
To enhance auditing and troubleshooting, we’ve introduced new webhook and audit log events to track the completion of certain secret backfill scans on repositories.
The events specify the type of backfill scan completed (e.g., Git backfill or issues backfill) and the secret types scanned, including custom patterns. Note that secrets detected through Copilot Secret Scanning are not included.
Backfill scans cover the entire repository and occur when secret scanning is enabled or patterns are updated. These events do not include information on incremental scans, which focus on new content pushed to a repository.
A repository must have a GitHub Advanced Security license to access these events.
To try it, just pick o1 (Preview) from the model picker in Visual Studio Code or in the full-screen, immersive Copilot Chat experience at github.com/copilot.
Access to the o1 model is currently in public preview, so if you’re a Copilot Business or Copilot Enterprise subscriber, an administrator must enable access to the o1 family of models before o1 shows up in the model picker.
Support for o1 is coming soon to Visual Studio, and we’re working to bring the model picker to the JetBrains IDEs.
OpenAI o1 is also available in GitHub Models – to learn more, check out the changelog.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
GitHub Models makes it easy for every developer on GitHub to build AI features and products, with access to top AI models via a playground, API, and more.
Today, we’ve added access to OpenAI’s brand new o1 model. The new o1 model replaces o1-preview, and offers even better performance in complex tasks. You can learn more about this launch and its availability on both GitHub Models and Copilot in our blog post.
Free Tier Support for GitHub Copilot Now Available on JetBrains IDEs
We’re excited to introduce the Free Tier for GitHub Copilot, now available for JetBrains IDEs! Starting today, you can enable GitHub Copilot in your JetBrains IDE with just a GitHub account—no trials or subscriptions required.
What’s included in the Free Tier?
The Free Tier provides everything you need to get started with GitHub Copilot:
* 2000 code completions/month
* 50 chat requests/month
* 64k context window for a seamless development experience
If you reach the limits, you can explore additional tiers to continue using GitHub Copilot’s powerful features.
Why it matters
GitHub Copilot in JetBrains IDEs empowers you to write code faster, focus on creative problem-solving, and enhance productivity—all with an AI assistant right in your IDE. With the Free Tier, more developers than ever can access these tools and start improving their workflows today.
Get started
We’d love for you to try the GitHub Copilot Plugin for JetBrains IDEs and share your thoughts. Your feedback plays a crucial role in helping us improve the product.
Join the discussion
Connect with the developer community in the GitHub Community Discussion to share your experiences, ask questions, and provide feedback.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
On January 20th, 2025, Dependabot will end support for npm version 6, which has reached its end-of-life. If you continue to use npm version 6, there’s a risk that Dependabot will not create pull requests to update dependencies. In that case, we recommend updating to a supported release of npm. As of December 2024, the newest supported release of npm is version 11. View NPM’s official documentation for more information about supported releases.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
The Windows 2025 server image for GitHub Actions hosted runners is now available in public preview. To start using this image in your Actions workflows, update your workflow file to include runs-on: windows-2025.
Please note that the Windows 2025 image has a different list of installed tools and tool versions. See the full list of changed software including differences in the announcement.
If you spot any issues with your workflows when using Windows Server 2025, or if you have feedback on the software installed on the image, please let us know by creating an issue in the runner-images repository. While the runner image is in preview, you may experience longer queue times during peak usage hours.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
The GitHub Models playground now shows your real-time token usage, including both input and output counts, as well as latency information in its responses. The analytics are accessible via the top bar, helping you more efficiently optimize prompts, evaluate model costs, and monitor response times.
Additionally, clicking on the information in the top bar now opens a modal with more details about the token and latency metrics:
GitHub Models makes it easy for every developer on GitHub to build AI features and products, with access to top AI models via a playground, API, and more.
CodeQL build-mode: none scans can now access private dependencies stored in private registries (e.g. Artifactory) for Java and C# projects. This makes your scans more comprehensive, ensuring you receive all important alerts regardless of where your dependencies are stored.
Previously, build-mode: none code scans with the default setup were unable to fetch code for dependent packages stored in private registries, which could result in incomplete analysis. Now, organization administrators can configure access credentials for private registries at the organization level. This enhancement allows CodeQL scans in child repositories to retrieve all necessary dependencies, enabling comprehensive code analysis when using the code scanning default setup.
This feature is currently in public preview for GitHub Advanced Security customers.
With the new GitHub Copilot Free plan, anyone can experiment with GitHub Copilot in Visual Studio Code and on GitHub! By simply signing in with your personal GitHub account, you will have access to 2000 Code Completions and 50 chat messages per month!
Here are a few things to try out today:
Accelerate your development with code completion
Execute edits across multiple files with Copilot Edits
Choose the model that works best for you, starting with Anthropic’s Claude 3.5 Sonnet
Access the Copilot Extensions to customize your development experience
Elevate your coding skills with our redesigned Copilot Chat, now featuring a dedicated home on GitHub.
What’s new in Copilot Chat on GitHub:
Immersive chat experience at github.com/copilot: Copilot is now just one click away, offering a seamless and immersive chat directly on GitHub.
Smarter and faster responses: Whether you’re brainstorming, problem-solving, or just exploring ideas, Copilot’s answers are sharper, richer, and more naturally attuned to your needs.
Real-time interaction with your codebase: Ask questions and get immediate answers about your codebase, helping you understand how things work faster than ever.
Generate and refine code effortlessly: Use conversational prompts to create and refine code snippets or entire files. Iterate seamlessly until you achieve the desired outcome.
Navigate GitHub with natural language: Summarize issues and pull requests, retrieve specific information, and explore repositories without navigating through the UI.
Leverage a variety of models: Choose from different AI models to get the best results based on your specific use case.
Find and return to previous chats: Easily revisit past conversations, keep track of important insights, code iterations and decision-making processes by accessing your entire conversation history whenever you need it.
Expanded capabilities across your entire codebase
As part of this update, we’ve removed limits on how many repositories you can index. Now, you can enjoy the full capabilities of Copilot Chat across your entire codebase, whether you’re working on multiple projects or a large monolith.
Your feedback helps us continue to improve. Let us know what you think using the in-product feedback option or pop it into the GitHub Community at any time.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
You can now more easily filter secret scanning alerts, with new filter options and advanced filtering.
Enterprise and organization level list views now include a new menu with commonly used and suggested filter options, like bypassed secrets, publicly leaked secrets, and those with enterprise duplicates. The repository level list view now supports a new “advanced filtering” menu.
The experimental toggle has been removed from the alert list header UI, but you can still access it from the sidebar navigation menu and with the results:experimental filter.
Public leak and multi-repository indicators are fully supported across list views, including alert list views and the REST API. In the UI, in addition to menu options, you can access these filters with is:multi-repository and is:publicly-leaked. These indicators are also included in webhook and audit log event payloads for secret scanning alerts.
What are public leak and multi-repo labels?
To help you triage and remediate secret leaks more effectively, GitHub secret scanning now indicates if a secret detected in your repository has also leaked publicly with a public leak label on the alert. The alert also indicates if the secret was exposed in other repositories across your organization or enterprise with a multi-repository label.
These labels provide additional understanding into the distribution of an exposed secret, while also making it easier to assess an alert’s risk and urgency. For example, a secret which has a known associated exposure in a public location has a higher likelihood of exploitation. Detection of public leaks is only currently supported for provider-based patterns.
The multi-repository label makes it easier to de-duplicate alerts and is supported for all secret types, including custom patterns. You can only view and navigate to other enterprise repositories with duplicate alerts if you have appropriate permissions to view them.
Both indicators currently apply only for newly created alerts.
You can now use the new “Improve Prompt” button next to your system prompt in the Models Playground.
A system prompt is a predefined instruction or guideline that sets the behavior and tone for an AI model, helping it respond in a specific way to user inputs. This AI-powered tool will refine and optimize your prompt to help you get the best possible results from your chosen model.
GitHub Models makes it easy for every developer on GitHub to build AI features and products. Easily try, compare, and implement models in your code for free via the playground or API.
