Announcing GitHub Copilot Free

GitHub Copilot Free

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

To get started, visit our immersive experience and learn more in our announcement blog.

Stay tuned for updates as we work to continually enhance your developer experience and be sure to share feedback in Discussions.

Copilot Chat on GitHub is now generally available for all users

Screenshot of GitHub Copilot Chat immersive mode

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.

See more

Improved filtering for secret scanning alerts

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.

Learn more

Learn more about reviewing alert labels and how to secure your repositories with secret scanning. Let us know what you think by participating in our GitHub community discussion or signing up for a 60 minute feedback session.

See more
View all changes