티스토리 수익 글 보기

You can now manage GitHub Code Quality availability separately from Code Security in GitHub Advanced Security policies. This gives you more flexibility to make GitHub Code Quality available across your enterprise without unintentionally enabling Code Security.

This update includes the following changes:

• The Advanced Security enterprise policy settings no longer mention the Code Quality feature.
• A dedicated policy page is now available to manage GitHub Code Quality at the repository level, similar to the existing Advanced Security policy experience.

Learn more about using enterprise policies to control access to GitHub Code Quality in our Code Quality documentation.

The post GitHub Code Quality enterprise policy appeared first on The GitHub Blog.

GitHub now warns you by email as your included usage approaches its monthly thresholds across Actions, Packages, Git LFS, and Codespaces.

GitHub now sends email notifications when your included usage reaches 90% and 100% during a billing period. This helps you stay ahead of unexpected overage charges or workflow disruptions.

Notifications are sent for the following metered products:

• Actions minutes
• Actions storage
• Packages bandwidth
• Packages storage
• Git LFS bandwidth
• Git LFS storage
• Codespaces core hours
• Codespaces storage

Each email identifies the account, product, approximate usage versus included allowance, and current billing period. It also includes a direct link to budgets for further monitoring.

You can opt in or out of these notifications from the Included usage alerts control on the “Budgets & alerts” page. This is available to enterprise admins, organization admins, and billing managers.

To learn more, see Included usage alerts.

The post Email notifications for included usage thresholds appeared first on The GitHub Blog.

We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions):

The Gemini 3 Pro deprecation date is accelerated due to provider deprecation.

Please update your workflows and integrations to use supported models before these dates. Copilot Enterprise administrators may need to enable access to alternative models through their model policies in Copilot settings. As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you’ll see the model in the Copilot Chat model selector in VS Code and on github.com. No action is required to remove the models once they have been deprecated.

GitHub Enterprise customers with questions or concerns are encouraged to reach out to their account manager for further assistance.

Share your feedback

To learn more about the models available in Copilot, see our documentation on models and get started with Copilot today.

Join the GitHub Community to share your feedback.

The post Upcoming deprecation of Gemini 3 Pro and GPT-5.1 models appeared first on The GitHub Blog.

On February 13, 2026 we announced changes to the required network configuration for Copilot coding agent, taking effect on February 27.

These changes only affect teams running Copilot coding agent on self-hosted runners or larger runners with Azure private networking.

These changes have now taken effect. Copilot will apply subscription-based network routing, connecting to a different host depending on the Copilot plan of the user who initiated the agent task:

• Copilot Business: api.business.githubcopilot.com
• Copilot Enterprise: api.enterprise.githubcopilot.com
• Copilot Pro and Pro+: api.individual.githubcopilot.com

If your network is still configured to allow connections to api.githubcopilot.com for Copilot coding agent, you can now drop this host from your allowlist.

The post Network configuration changes for Copilot coding agent now in effect appeared first on The GitHub Blog.

Copilot usage metrics now includes plan mode telemetry. Enterprises can track adoption and engagement trends for plan mode alongside existing Copilot metrics, enabling a more complete view of how teams are implementing plans directly in their IDE.

Availability

• Plan mode telemetry is included as part of the broader Copilot usage metrics experience. Please ensure Copilot usage metrics is enabled for the enterprise or organization.
• Telemetry is supported for JetBrains, Eclipse, Xcode, and VS Code Insiders at the enterprise, organization, and user-level. General release for VS Code is expected soon.
• Within the API response, usage will be denoted by chat_panel_plan_mode under the keys totals_by_feature, totals_by_language_feature, and totals_by_model_feature.
• Within the dashboard UI, view plan mode breakdowns for request and model usage under Insights > Copilot usage.

Important note

Telemetry for plan mode used to be mixed in with “Custom”. Now that it’s properly broken out, you may see a dip in “Custom” usage. This may affect dashboard charts like “Requests per chat mode” and “Model usage per chat mode”.

Join the discussion within GitHub Community.

The post Copilot metrics now includes plan mode appeared first on The GitHub Blog.

GitHub Copilot usage metrics reports now return a consistent user_login value for Enterprise Managed Users (EMU). Previously, some reports could include a suffix in user_login, which made it harder to match results across GitHub APIs.

The post Copilot metrics reports now return consistent usernames for Enterprise Managed Users appeared first on The GitHub Blog.

Copilot enterprise usage metrics coverage has expanded to now include Copilot CLI telemetry.

With this update, your enterprise metrics can include CLI-specific activity and usage totals, such as:

• Daily active CLI users
• CLI request and session counts
• Token usage totals, including average tokens per request

Why this matters

• Track CLI adoption across your enterprise and spot where enablement or support is needed.
• Compare usage patterns across environments so you can understand how developers use GitHub Copilot day to day.
• Use token usage totals to better understand consumption trends and plan for rollout over time.

Join the discussion within GitHub Community.

The post Copilot usage metrics now includes enterprise-level GitHub Copilot CLI activity appeared first on The GitHub Blog.

GitHub Copilot usage metrics is now generally available, giving you a single place to see how your teams adopt and use Copilot. This way you can track trends, make informed decisions about rollout, and build reports that fit your organization.

Since the public preview at Universe 2025, Copilot usage metrics has expanded with organization-level visibility, fine-grained access controls, data residency support, and more. Here’s what you can expect now that it’s generally available.

What’s included

Dashboards

• Copilot usage dashboard provides clear, actionable insights into how your teams are using GitHub Copilot. The dashboard provides visibility into code completion activity, IDE usage, model and language breakdown, and more.
• Code generation dashboard gives a directional measure of Copilot’s output by quantifying the lines it suggested, added, or deleted across completions, chat, and agent features.
• Enterprise and organization-level granularity allows enterprise and organization owners to track adoption and usage trends for their teams without relying solely on enterprise-wide aggregates.

APIs

• Enterprise-level: Get a bird’s eye view of all Copilot usage across your entire enterprise for aggregate analysis on user engagement, Copilot usage, pull request throughput, and more.
• Organization-level: Organizations can programmatically access their own Copilot usage to understand how teams are engaging with Copilot, spot trends, and assess enablement efforts.
• User-level: Analyze individual Copilot usage for a specific day to support enablement and identify where teams may need training or better documentation.

Check out our API documentation to learn more.

Access and availability

• For access, navigate to your enterprise account → AI Controls → Copilot → Metrics → Copilot usage metrics. You should then see the dashboard under Insights → Copilot usage or Code generation. Please also ensure you are either an Enterprise Administrator, Billing Manager, or have the proper fine-grained permissions to have access to Copilot metrics.
• Fine-grained access controls let you share visibility with the right people using custom enterprise roles, such as View enterprise Copilot metrics, without requiring full admin access.
• Added support for GitHub Enterprise Cloud with data residency so enterprises with residency requirements can access Copilot usage dashboards and API reporting.

What’s next

Today’s release delivers the data foundation for understanding Copilot adoption across your organization. The next question many leaders are asking is “is it working?” We’re building toward that answer—connecting usage patterns to engineering outcomes so you can move from tracking adoption to measuring impact. We’ll share more as these capabilities become available.

To get started, visit Copilot usage metrics documentation. Join the discussion within GitHub Community.

The post Copilot metrics is now generally available appeared first on The GitHub Blog.

GitHub Actions now supports uploading and downloading non-zipped artifacts within workflows. Previously, when you uploaded an artifact using the actions/upload-artifact action it was automatically zipped. Downloading it using the actions/download-artifact action or directly from the browser would download this file zipped. Many users found this additional compression frustrating and told us it added significant friction to their workflows.

We have added support to these actions so that you can upload unzipped artifacts and also download them unzipped. This solves three major problems that you raised to us:

• You no longer have to unzip when downloading a single file via the browser.
• If your browser supports viewing the file type natively, you can view files directly in your browser. This is great for simple HTML files (without links to CSS or JS), images, or markdown. This includes mobile browsers as well.
• If you upload a compressed file to maintain permissions or reduce size, you no longer have a compressed file within another compressed file (i.e., the double zip problem).

These changes only apply to artifacts uploaded with actions/upload-artifact v7 where you have set the archive parameter to false. This value is currently defaulted to true for backwards compatibility. Previously uploaded artifacts and any artifacts uploaded with older versions of the action will continue to be zipped. You will also need to update to v8 of actions/download-artifact if you use that action.

The post GitHub Actions now supports uploading and downloading non-zipped artifacts appeared first on The GitHub Blog.

The download URLs returned by the GitHub Copilot usage metrics API now come from a new endpoint. Your report data, the API contract, and the response schema haven’t changed.

Action required

• If your firewall rules allowlist specific CDN domains, add copilot-reports-production-*.b01.azurefd.net alongside the existing copilot-reports-*.b01.azurefd.net pattern.
• If you download reports using the download links in the dashboard UI, you don’t need to make any changes.

To view the current list of allowlist domains, see the GitHub Copilot allowlist reference documentation. Join the discussion within GitHub Community.

The post Copilot metrics report URLs update appeared first on The GitHub Blog.