惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

aimingoo的专栏
aimingoo的专栏
Engineering at Meta
Engineering at Meta
有赞技术团队
有赞技术团队
博客园_首页
Apple Machine Learning Research
Apple Machine Learning Research
Vercel News
Vercel News
G
Google Developers Blog
Blog — PlanetScale
Blog — PlanetScale
IT之家
IT之家
MongoDB | Blog
MongoDB | Blog
Y
Y Combinator Blog
B
Blog
The GitHub Blog
The GitHub Blog
M
MIT News - Artificial intelligence
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Stack Overflow Blog
Stack Overflow Blog
C
Check Point Blog
Microsoft Azure Blog
Microsoft Azure Blog
D
DataBreaches.Net
I
InfoQ
Recent Announcements
Recent Announcements
阮一峰的网络日志
阮一峰的网络日志
腾讯CDC
H
Help Net Security

Archive: 2026 - GitHub Changelog

MAI-Code-1-Flash for Copilot Business and Copilot Enterprise - GitHub Changelog GitHub Desktop 3.6: Worktrees and deeper Copilot integration - GitHub Changelog Copilot code review: Analysis depth and efficiency updates - GitHub Changelog Enterprise-managed settings now support strictKnownMarketplaces in VS Code and GitHub Copilot CLI - GitHub Changelog Saved views for repository issues - Public Preview and adjustable row heights in projects - GitHub Changelog More control over your GitHub-hosted runners - GitHub Changelog Actions steps can now be run in parallel - GitHub Changelog npm adds preventive account protection for high-impact accounts - GitHub Changelog Red Hat Enterprise Linux runner images are now in public preview - GitHub Changelog GitHub Copilot for Jira is now generally available - GitHub Changelog Self-service credential revocation for incident response - GitHub Changelog Changes to model selection for Free and Student plans - GitHub Changelog Secret scanning adds extended metadata for Replicate secrets - GitHub Changelog Fetch Code Quality findings via REST API - GitHub Changelog Automatic Dependabot access to GitHub-hosted registries - GitHub Changelog Copilot CLI: New terminal interface is generally available - GitHub Changelog Deprecation of Python 3.9 for Dependabot - GitHub Changelog GitHub Copilot app support for BYOK - GitHub Changelog New features and Claude as agent provider preview in JetBrains IDEs - GitHub Changelog AI credits consumed per user now in the Copilot usage metrics API - GitHub Changelog Upcoming deprecation of Opus 4.6 (fast) - GitHub Changelog MAI-Code-1-Flash available on more Copilot surfaces - GitHub Changelog Copilot code review: AGENTS.md support and UI improvements - GitHub Changelog Detecting Duplicate Issues - Public Preview and issue fields MCP support for GitHub Issues - GitHub Changelog Copilot-authored pull requests now included in author searches - GitHub Changelog Repository switcher generally available in global navigation - GitHub Changelog Actions: Build custom images from custom images - GitHub Changelog Safer pull_request_target defaults for GitHub Actions checkout - GitHub Changelog Control who and what triggers GitHub Actions workflows - GitHub Changelog Generated release notes credit you for Copilot pull requests - GitHub Changelog
Cost centers now support enterprise teams - GitHub Changelog
Allison · 2026-06-25 · via Archive: 2026 - GitHub Changelog

Cost attribution across your enterprise can now follow your team structure. You can add enterprise teams as resources in a cost center, and all usage incurred by team members is attributed to that cost center. As membership changes, whether through manual updates or identity provider (IdP) sync via SCIM, attribution updates automatically, with no reassignment required.

Enterprise teams organize who belongs to a cost center. Budgets and usage caps attach to the cost center itself, so adding a team is how you keep membership current, not how you set spending limits.

This is especially useful for enterprises that already use enterprise teams to manage access and roles across organizations. You can use those same teams to drive cost attribution, keeping your billing structure aligned with your org structure. It is also the foundation for capping spend by group: once a team is in a cost center, you can set a budget on that cost center and every member inherits it.

Who can use this feature

Enterprise owners and billing managers on GitHub Enterprise Cloud.

To get started, go to your enterprise’s Billing and licensing settings, open Cost centers, and add an enterprise team under “Resources” when creating or editing a cost center.

To learn more, see Control GitHub costs at scale.

Join the discussion or submit feedback within GitHub Community.