AI觉醒星球
Awakening is here
Knowledge File / AI小生意项目库
2026-07-09 0 浏览 会员

通过MDM在VS Code和CLI中部署受管的Copilot设置

企业管理员现在可以通过设备管理(MDM)和配置文件直接在设备上交付受管的GitHub Copilot设置,支持VS Code和CLI。

SOURCE / AI小生意项目库 MIN / 9 ACCESS / 会员 POST / 2026-07-09 04:38:56

原贴

查看原文
作者:Allison 来源站点:github.blog 原贴时间:

原文

Enterprise administrators can now deliver managed GitHub Copilot settings directly to devices through native mobile device management (MDM) and file-based configuration, in addition to the existing server-managed channel. This is generally available for GitHub Copilot CLI and VS Code. Device-level deployment lets you enforce Copilot governance using the same tools you already use to manage endpoints. You can push settings through Microsoft Intune, Jamf, or Group Policy, or deploy a configuration file with Chef, Puppet, or Ansible. Because settings are read from the device, they apply consistently across VS Code and Copilot CLI, regardless of how a developer signs in. You can deliver managed settings through any of three channels, all of which use the same keys and values. Native MDM reads OS-level managed preferences. On Windows, settings come from the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\GitHubCopilot registry key. On macOS, they come from managed preferences for the com.github.copilot domain. File-based reads a managed-settings.json file from a well-known path (i.e, /Library/Application Support/GitHubCopilot/managed-settings.json on macOS, %ProgramFiles%\GitHubCopilot\managed-settings.json on Windows, and /etc/github-copilot/managed-settings.json on Linux). File-based settings must be owned by root and cannot be world-writable or symlinked. Server-managed resolves settings from the developer’s signed-in GitHub account via managed-settings.json in your organization’s .github-private repository. When more than one channel provides settings, the highest-precedence channel wins outright, in this order: The device-level channels support the same managed setting keys as the server-managed channel, including: permissions.disableBypassPermissionsMode telemetry.* for OpenTelemetry export configuration Scalar settings use their dot-separated key directly, while structured settings such as enabledPlugins are supplied as a JSON string value. Additional keys will be added over time. To learn how to deploy managed settings to your devices, see Deploy Copilot managed settings . For the full list of keys and the settings they control, see Configure enterprise managed settings .

中文翻译

企业管理员现在可以通过原生移动设备管理(MDM)和基于文件的配置,以及现有的服务器管理渠道,直接将受管的GitHub Copilot设置交付到设备。这适用于GitHub Copilot CLI和VS Code。

核心信息

企业管理员现在可以通过设备管理(MDM)和配置文件直接在设备上交付受管的GitHub Copilot设置,支持VS Code和CLI。

  • 企业管理员现在可以通过设备管理(MDM)和配置文件直接在设备上交付受管的GitHub Copilot设置,支持VS Code和CLI。
  • 原贴提到:Enterprise administrators can now deliver managed GitHub Copilot setting
  • 来源:github.blog
试看内容

成为会员查看完整内容

你已经看到了这篇内容的前置整理,剩余深度部分仅对会员开放。

详细解读 信息差价值 参考来源
成为会员查看完整内容
上一篇 面向VS Code和CLI的企业托管OpenTelemetry导出 下一篇 Grok 4.5 相比 Fable 5 和 GPT 5.5 如此便宜,基准测试差距可能没那么重要