tag: Github-Enterprise · 12 items
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: If your org pays for GitHub Enterprise and Copilot separately, this bundling change is worth reviewing with your account team to consolidate licensing and potentially reduce complexity or cost. No deadline, but address it in the next contract or planning cycle.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Learn: If your org uses GitHub Enterprise Managed Users, review whether any accounts were incorrectly deleted (rather than suspended) during June 1–13, 2026 via SCIM deprovisioning — particularly any service or bot accounts your teams rely on.
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub Enterprise Cloud feature enables ruleset-based OSS license checks in pipelines; schedule evaluation to enforce centralized license policy as a supply-chain hardening step this quarter.
- Leader — Plan: GA tooling for enforcing OSS license policy at scale on GitHub Enterprise Cloud directly addresses legal/compliance risk from dependency licensing; evaluate enabling it as a formal org standard this planning cycle.
- Signals: GA announcement
- Platform/SRE — Act: If your org uses GitHub Enterprise Cloud with data residency, audit any internal tooling, Terraform GitHub provider clients, or API automation that may negotiate TLS using only X25519 before October 7 — connections from those clients will break.
- CI/CD — Act: Verify that CI runners and pipeline scripts connecting to GHE.com with data residency use a TLS stack that offers multiple key-agreement algorithms, not X25519 exclusively; the hard cutoff is October 7, 2026.
- Leader — Skip
- Platform/SRE — Learn: A new GA GitHub Enterprise Cloud governance control that tightens human access to sensitive org actions; no infrastructure change required, but worth understanding when designing access-control policies.
- CI/CD — Plan: Evaluate which release and deployment actions qualify as high-impact in your org and whether enabling proof-of-presence would require changes to release-approval workflows; no deadline, but this is a concrete supply-chain hardening step to schedule this quarter.
- Leader — Plan: Evaluate rolling out proof-of-presence as an org-wide GitHub Enterprise Cloud policy to reduce insider-threat and account-takeover risk on sensitive actions; no deadline, but a meaningful security governance improvement to bring into your next planning cycle.
- Platform/SRE — Skip
- CI/CD — Learn: A full exportable inventory of SSH keys, PATs, and OAuth tokens touching the enterprise is useful context for supply-chain hygiene thinking, but it introduces no pipeline mechanic to change today.
- Leader — Plan: Schedule a review of GitHub Enterprise credential inventory exports as part of your next access-review or compliance cycle; the capability directly supports audit readiness for SOC 2 / ISO 27001 controls around privileged access.
- Platform/SRE — Learn: Reduces friction for credential management in GitHub Enterprise Cloud environments, but this is an admin/policy feature with no infrastructure operational urgency.
- CI/CD — Plan: If pipelines use classic PATs or SSH keys in SSO-enforced orgs, automating authorization can eliminate manual unblocking steps — worth scheduling a review of affected credentials and updating provisioning workflows.
- Leader — Learn: Marginally improves developer onboarding and access management in GitHub Enterprise Cloud; no strategic, cost, or vendor-risk implication requiring a decision.
- Platform/SRE — Plan: GHES 3.22 GA means teams running self-hosted GHES should plan an upgrade evaluation this quarter. No forced-upgrade deadline is present, but a new minor release with platform-wide changes warrants scheduling a controlled upgrade project.
- CI/CD — Learn: If your pipelines run on GitHub Actions hosted on GHES, this version bump may eventually surface new runner or Actions capabilities, but the release summary is too thin on CI/CD specifics to warrant a pipeline change today.
- Leader — Learn: GHES 3.22 adds capabilities including Copilot CLI for administrators — worth tracking as context for AI-tooling standardization, but no licensing, pricing, or strategic forcing function is present in this release.
- Signals: GA announcement
- Platform/SRE — Learn: RC status caps this at Learn; worth tracking if you self-host GHES, but wait for GA before planning an upgrade.
- CI/CD — Learn: Pre-GA release; monitor for GA before evaluating pipeline or Actions changes that may ship in 3.22.
- Leader — Skip
- Signals: pre-GA (alpha/beta/RC/preview)
- Platform/SRE — Skip
- CI/CD — Plan: If a GitLab-to-GitHub migration is on the roadmap, GEI reaching GA means self-serve tooling is now available for scoping the pipeline migration project.
- Leader — Plan: If your org is evaluating consolidating from GitLab to GitHub Enterprise Cloud, the GA of self-serve migration tooling removes a key friction point worth including in the next planning cycle.
- Signals: GA announcement
- Platform/SRE — Act: If you operate GitHub Enterprise Server, review the new security requirements for support bundle uploads and ensure your GHES instance is compliant before August 18, 2026, or uploads will be rejected, hampering incident troubleshooting.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Plan: Enterprises standardized on GitHub Enterprise Cloud can now automate VSS seat assignments via REST API, enabling programmatic license auditing and allocation at scale — worth scheduling into the licensing management workflow.