Skip to content

GitHub Copilot Enterprise – Copilot knows about repositories, releases, commits + more May 2024 updates

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

Copilot Chat in GitHub.com 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 GitHub.com, 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 GitHub.com, 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 GitHub.com, and ask Copilot to Summarize the changes in this commit

Don’t know where to begin? Copilot Chat on GitHub.com 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.

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

Starting today, we will begin work towards the sunset of tag protections, with a full deprecation planned for August 30, 2024. See below for a full sunset timeline. You can migrate existing tag protections with the import to ruleset feature.

We launched repository rules last year to meet the needs of tag protection rules, while also scaling support to provide new functionalities like org-wide rules, granular restrictions for creating, reading, and updating events, and a more granular bypass model that does not require repository administrator permissions. As we such, we will sunset tag protections in favor of our ongoing investment in the repository rulesets platform.

You can import existing tag protection rules today with the existing migration feature. If no action is taken before the sunset date, GitHub will migrate all existing tag protections into a corresponding ruleset.

When are changes happening?

GitHub.com Timeline

  • May 30 : Repositories without tag protection rules will no longer be able to add new protection rules via the GitHub.com UI
  • July 24 through August 14 : A series of API brownouts will be run, see below for additional details on dates and times.
  • August 30, 2024: All tag protection rules will be migrated to a new tag ruleset. All REST and GraphQL API endpoints will be deprecated

GitHub.com API Timeline

  • May 30: API responses will include a deprecation notice
  • July 24: 1 hour API brownout
  • August 7: 8 hour API brownout
  • August 14: 24 hour API brownout
  • August 30: The tag protection rule API will begin responding with NULL data
  • The tag protection rules API will be deprecated in the next calendar version

GitHub Enterprise Server Timeline

  • Version 3.14: Tag protection rules will be marked for deprecation with an in-product banner and API responses will include a deprecation notice
  • Version 3.15: No changes will be made
  • Version 3.16: Tag protection rules will be migrated to a ruleset and the tag protection rule feature will no longer be available

Join the discussion within GitHub Community.

See more