Author name: ITMAITY

GPU utilization is a data problem before it is a compute problem, and the three forms of data are how you solve it.   ​  ​GPU utilization is a data problem before it is a compute problem, and the three forms of data are how you solve it. AI Data Platform Blog | Dell

Why “unified namespace” is a polite way of pretending data has no mass, and what the three forms of data actually let you move.   ​  ​Why “unified namespace” is a polite way of pretending data has no mass, and what the three forms of data actually let you move. AI Data Platform Blog | Dell

Inside Dell’s first global internship: meaningful work, real connections, and the launchpad turning interns into future leaders worldwide.   ​  ​Inside Dell’s first global internship: meaningful work, real connections, and the launchpad turning interns into future leaders worldwide. Innovation Blog | Dell

As demand for cloud and AI services continues to grow, datacenters are becoming more essential than ever. Communities also want to better understand how this infrastructure affects local resources, particularly water. At Microsoft, water stewardship has been a priority since our first datacenter builds in the early 2000s and remains a core part of our strategy today and into the future. It underpins both our Community-First AI Infrastructure initiative and our company-wide commitment to become water positive by 2030, meaning we will replenish more water than we withdraw. We are pairing our progress with continued transparency so people can understand not only how much water we use, but also how we are working to reduce that use over time. Through continuous innovation and advancements in cooling technologies, we have improved our water use effectiveness (WUE), measured in liters per kilowatt-hour (L/kWh), by nearly 90% since our first generation of datacenters in the early 2000s. Our average WUE has decreased from 2.3 L/kWh to 0.27 L/kWh in 2025, reflecting decades of innovation and our ongoing commitment to reducing the water intensity of our datacenters while meeting the growing demand for cloud and AI services. Across our entire owned fleet of datacenters, we are committed as a company to a 40 percent improvement in datacenter water-use intensity by 2030. As of 2025, we have reduced our water-use intensity by 25 percent, putting us well over halfway toward our goal. This strong progress reflects the impact of our continued investments in water-efficient cooling technologies, operational improvements and responsible water management practices.* In FY25, Microsoft reached an important milestone toward its 2030 water positive commitment, replenishing more water than it withdrew across its global operations for the year. We have made this progress by decoupling datacenter growth from water use through resilient, responsible water stewardship practices and the deployment of increasingly efficient cooling technologies — demonstrating that digital growth and sustainable water management can advance together. We are committed to building on this progress and working toward sustaining water positive performance over time as we continue advancing toward our 2030 goal. Early water stewardship by design Beginning with some of our earliest datacenter designs, we prioritized water efficiency while minimizing impacts on energy use through the deployment of high-efficiency economizing chillers operating at elevated water temperatures. As early as 2008, we adopted direct air cooling with evaporative assist as the primary cooling approach across our datacenter fleet. This design uses significantly less electricity and up to 90% less water than traditional water-based cooling systems by relying on water only when outside temperatures exceed 85°F (29.4°C). In parts of Northern Europe, no water is required for cooling throughout the year, while in other cooler regions like Dublin and Amsterdam, water is used less than 5% of the time. In more temperate climates like Virginia, water is typically required only 10% of the year, while in the hottest climates like Phoenix, water use may increase to as much as 40% of the year. As a result, approximately 90% of our 2025 owned fleet operates using highly efficient, low- to zero-water cooling systems. YouTube Video Click here to load media While the majority of our existing datacenters are already highly water efficient, we did not stop there. In 2024, Microsoft introduced a new datacenter design optimized for AI workloads that consumes zero water for cooling during operations, further reinforcing our commitment to water stewardship by design. This chip-level cooling solution delivers precise zonal temperature control without water evaporation by recirculating water through a closed-loop, direct-to-chip cooling system. As our datacenter fleet continues to expand, the addition of these zero-water designs will further reduce Microsoft’s water use intensity over time. Datacenter cooling methods, explained: Cooling towers: Traditional systems that remove heat by evaporating water year-round. Hybrid fluid coolers: Evaporates water for cooling during hot summer conditions and switches to dry mode when ambient temperatures cool down. Direct air: Uses outside air for cooling, with little to no water use. Water is used only when outside air is above 85°F. Air cooled chillers: Uses mechanical refrigeration and outside air to remove heat from closed coolant loops with zero water evaporation. Liquid-cooled AI DCs: Uses closed-loop, direct-to-chip cooling to provide precise chip-level temperature control, removing heat efficiently with zero water evaporation. Modernizing cooling in existing datacenters with smarter controls Design innovation is only part of the story. We are also improving the efficiency of existing facilities that use water through a continuous focus on optimizing temperature and humidity setpoints, enabling more precise environmental control and eliminating overcooling. In addition, we regularly audit water use and compare actuals against design expectations using real-time weather data and operational analytics. This helps ensure our datacenters are performing as intended and enables us to quickly identify and address any unexpected water use. These efforts, combined with ongoing hardware and operational improvements, are all aimed at using as little water as possible. Specifically in our Phoenix, Arizona, datacenters, implementation of these advancements led to a 23% year-over-year improvement in WUE in FY25 alone. We are now deploying these advancements across our direct-evaporatively cooled datacenters globally. Operational improvements like these are one reason Microsoft has been able to report significant long-term reductions in water intensity across datacenter generations. They also point to the next phase of our work: expanding the use of recycled and alternative water sources wherever possible. Leveraging recycled, reused and non-potable water In addition to driving efficiency, we also prioritize using recycled, reused or non-potable water wherever possible in our operations. We have expanded the use of these non-potable water sources in some of our most water-intensive regions, helping reduce demand on freshwater supplies. For example, in Quincy, Washington, Singapore and San Antonio, Texas, three of our key locations for advancing water stewardship, we leverage 74%, 99% and 79% recycled, reused or non-potable water sources, respectively. Rainwater harvesting systems are now operational at select datacenters in the Netherlands, Sweden and Ireland, with additional installations planned in Canada, the United Kingdom, Finland, Italy,

Cloud operations are entering a new era as AI-driven and autonomous agents become a larger part of modern software systems. As software becomes increasingly agentic, the challenge is no longer just managing greater scale and complexity. Operators must also contend with systems that evolve faster, act more autonomously and interact across an expanding network of dependencies. As applications, models, APIs and infrastructure become increasingly interconnected, their behavior is harder to understand end to end. Systems no longer fail in isolation. They fail through interactions across dependencies, services and environments that are constantly changing in real time. To help organizations operate effectively in these increasingly dynamic environments, today we’re announcing the general availability of the Azure Copilot Observability Agent. Built on Microsoft Azure Monitor, it correlates signals across agents, applications, infrastructure and services to provide the context needed to operate confidently in this new environment. Observability becomes foundational in an agentic world In a recent survey of 250 IT decision-makers, Microsoft and Material found that 84% of organizations report increased cloud complexity, with 69% saying it is outpacing their current operating model. The impact is most acute across security, cost management and performance, and it extends across the entire operations lifecycle. As the pace and scale of change accelerate, no individual or team can realistically maintain the full context required to diagnose and resolve issues quickly enough. This is driving a shift toward agentic operations, where intelligence augments how systems are understood and managed. Observability is foundational to this shift. It provides the real-time understanding of system behavior that agents depend on to reason, adapt and act. Without a connected view across signals, even the most advanced agents lack the context required to operate reliably. From signals to resolution with the Observability Agent We designed the Observability Agent to help operators move more quickly from detection to understanding. It connects logs, metrics, traces, topology and operational context across environments, reducing the time it takes to identify the root cause of an issue. As telemetry spreads across systems, operators are often forced to piece together context across multiple tools. The Observability Agent addresses this fragmentation by reasoning across signals in real time and unifying that context into a single operational view. These agentic capabilities are integrated directly into existing workflows, helping teams move from investigation to resolution faster with clear, actionable insight. We’re already seeing customers use the Observability Agent to reduce manual effort, accelerate incident resolution and improve operational clarity: “The biggest value is speed! The [Azure Copilot] Observability Agent helps us resolve incidents faster and reduce operational overhead by turning logs, metrics and traces into plain English insights. These agents run deep investigations and provide remediation recommendations almost immediately, compared to hours or even days previously. Since adopting these capabilities, we’ve reclaimed an estimated 250 engineering hours monthly that are now redirected toward supporting new applications and features. We can use natural language to detect, diagnose and remediate issues faster than ever before.” — Narmada Krishnaswamy, Head of KPMG Audit Application Support and Operations “Azure Copilot Observability Agent helped us move from manual incident hunting to faster, AI-guided investigations. For PolicyVault, it pulls together the telemetry from our service, correlates it with Azure resource health and gives us actionable next steps based on the investigation. That means we’re not just seeing what broke; we’re getting a much clearer idea of why it happened and what to do about it, which saves us a lot of time during incidents.” — Vladimir Gusarov, Founder & CEO, PolicyVault “Azure Copilot’s Observability Agent helps us move faster from signal to insight. By bringing together our telemetry and guiding us toward likely root causes, it reduces the time and effort needed to investigate incidents and keeps our teams focused on what matters most.” — Theus Hossmann, Chief Technology Officer at Ontinue Beyond improving incident response, this shift reflects a new approach to cloud operations, where systems can continuously reason across signals and act on that understanding. Check out our Tech Community blog post to learn more about the Azure Copilot Observability Agent. From observability to agentic operations across the cloud lifecycle Observability is part of a broader shift to agentic operations. As systems become more autonomous, operations expand from understanding what is happening in production to continuously improving how those systems behave over time. In an agentic model, this forms a lifecycle. Systems generate signals, agents interpret those signals, take action and learn from outcomes. Over time, this creates a feedback loop where each operational cycle improves the next, increasing system resilience and efficiency. This shift requires more than better visibility. It requires a coordinated approach across the lifecycle, from observability and diagnosis to optimization and remediation where insight and action are tightly connected. As agents take on a greater role in that lifecycle, governance becomes central to how systems are trusted and controlled. Policy, auditability and guardrails ensure that actions taken by agents align with organizational intent and operate within defined boundaries. Human oversight remains essential, not as a bottleneck, but as a mechanism for building confidence and ensuring reliability as automation scales. This is where Azure is uniquely positioned. By bringing together observability, automation and governance within a connected platform, Azure enables organizations to move from isolated tools to an integrated operational model that spans the full lifecycle. Azure Copilot Observability Agent plays a key role in this model by grounding agentic systems in real-time operational context. As organizations build and deploy more agents, this foundation becomes critical for ensuring those systems operate effectively and responsibly. Cloud operations are shifting from reactive management to a continuous, agent-driven lifecycle of learning, adaptation and control. This vision of agentic cloud operations is already taking shape across Azure. Read our companion Azure Blog post for more details. Brendan Burns is a co-founder of the Kubernetes open source project and corporate vice president for Azure cloud-native open source and the Azure management platform including Azure Arc. He is also the author and co-author of several books

Today, Microsoft is announcing one of the largest single capacity additions in our history. In Pecos, Texas, we will build a new datacenter campus, expanding our global datacenter capacity by approximately 2 gigawatts (GW) to meet strong and sustained customer demand for AI and cloud services across industries and regions. Beyond the technology, this is a major investment in West Texas. We expect to support over 6,000 construction jobs at peak build-out and to create hundreds of permanent operational jobs that will add a new industry that supports the local economy when the new datacenter campus is operational. This multibillion-dollar datacenter campus investment over the next five to seven years reflects both the immediate needs we are seeing today and the future trajectory of AI and advanced compute, where reliable infrastructure at scale is essential to unlocking the next generation of innovation. This expansion is grounded in a simple principle: we build where our customers need us, and we build for the long term. We have a track record of doing exactly that in Texas. In the San Antonio region, where we have operated datacenters for nearly a decade, our investment has generated billions of dollars in local economic activity and supported thousands of local jobs. We are committed to delivering the same lasting value in Pecos. Meeting customer demand with reliable infrastructure Customer demand for AI and cloud services continues to grow rapidly, from startups building new applications to governments, healthcare providers and educational institutions modernizing critical systems. Meeting this demand requires not only more datacenter capacity, but capacity that is predictable, resilient and able to scale quickly. The datacenter campus in Pecos enables us to deliver on that need. By pairing new datacenter infrastructure with dedicated energy supply located onsite, we can bring capacity online at the pace our customers require while maintaining operational reliability. Critically, the energy infrastructure required to power this datacenter is being funded by Microsoft. We are paying for the new generation and supporting infrastructure needed to serve our own operations. The capacity we bring online in Pecos is built to meet our demand, ensuring that our growth strengthens, rather than strains, the energy resources the community relies on. Putting Community First in West Texas While meeting customer demand is critical, how we grow is equally important. At Microsoft, our Community First approach guides us where we build, own and operate our datacenters, including our new datacenter campus in Pecos. This work begins with a simple commitment: we show up as a lasting partner, not just a builder of infrastructure. As shared in our letter to the community in Pecos and Reeves County, we are approaching this project as a new neighbor, with a focus on partnership, transparency and listening. We recognize that earning trust takes time, and we are committed to ongoing engagement with local residents, leaders and organizations as this project moves forward. The region’s elected leadership has welcomed the investment. Reeves County Judge Leo Hung, the county’s top elected official, said: “We are excited to welcome Microsoft to Pecos. This investment reflects the strength of our region and its ability to support innovation at a global scale. It will create new opportunities for local businesses, support workforce development and reinforce Pecos as a place where forward-looking companies can grow and thrive.” Our Community First approach in this region focuses on three priorities: 1. Listening and engaging early We engage early and often through community meetings, local partnerships and ongoing communication across the life of the project, which gives residents multiple ways to ask questions and share feedback, just as we have in other Texas communities. 2. Creating local economic opportunity This project is built to drive lasting regional growth. As well as supporting thousands of construction jobs, the hundreds of permanent operational roles will add a new industry to the local economy. We will also invest in workforce development and small-business support. We are focused on ensuring that local residents are prepared to take advantage of the opportunities created by the AI economy. This is part of a sustained commitment to the region, building on more than a decade of experience in Texas, including our operations in San Antonio: A snapshot of Microsoft’s long-term impact in San Antonio, the kind of partnership we are bringing to Pecos. Near San Antonio, where we have operated for nearly a decade, our Datacenter Academy partners with local colleges to prepare students for datacenter careers, including a $545,000 investment that has already reached more than 450 students. Statewide, workforce programs like TechSpark have helped create more than 1,100 jobs and engaged 20,000 Texans in digital skilling. We will bring the same model of local hiring, training and small-business support to West Texas. 3. Partnering for lasting community impact Our investment reaches well beyond the datacenter, into education, digital inclusion and nonprofit partnerships. In fiscal year 2024, Microsoft and its employees contributed $11 million in cash and $103.3 million in donated software and cloud technology to more than 10,000 Texas nonprofits, alongside 42,000+ employee volunteer hours. In Pecos, we will direct that same commitment toward the priorities that matter most to West Texas residents. Advancing sustainability through innovation As we expand our datacenter footprint, we remain equally committed to building and operating our infrastructure in ways that reduce environmental impact. Energy and emissions This includes improving energy efficiency across our infrastructure, from compute to hardware, and building on the 4.7 GW of renewable electricity we have already contracted for our electricity use in Texas, advancing carbon-free electricity through renewable generation and other technologies. This investment is intentionally designed with flexibility in mind, allowing Microsoft to adjust capacity over time as demand evolves. At launch, the datacenter campus will operate with a co-located natural gas power facility, an arrangement known as “behind the meter.” This serves the campus directly and independently of the public grid, so this demand does not take from the current grid. The plant’s design will integrate state-of-the-art air emissions controls, such as

Welcome back to GitHub for Beginners. This is the final episode of the season, and we’ve covered a lot so far. Make sure to check out our other episodes to see all the various topics we’ve discussed. Today, we’re going to spend some time answering some questions that people often have, especially when they’re first getting started. So without further ado, let’s jump right in. As always, if you prefer to watch the video or want to reference it, we have all of our GitHub for Beginners episodes available on YouTube. What is SSH and how do I add my SSH key to GitHub? An SSH key is a secure shell key. It’s a pair of files on your computer that has two parts: a private key and a public key. The private key stays on your computer and should never be shared. The public key is what you share with platforms like GitHub. When you store your public key on GitHub, git uses your private key to confirm your identity when you push and pull code. In order for you to be authenticated, your public key on GitHub needs to match the private key on your computer. So how do you do this? Let’s create a key pair and add your public key to GitHub now. (And remember, if you prefer a video walkthrough, that is available.) Open up a terminal and enter the following command. Remember to replace the email placeholder with your email address you use to log into GitHub. ssh-keygen –t ed25519 – C YOUREMAIL@DOMAIN.COM When it prompts you to enter a file to save the key, press Enter to accept the default file and location. Enter a passphrase that you’ll remember. Note that the terminal will not display what you type, so be careful not to have any typos! Reenter your passphrase. This will create your new SSH key. Now you want to add it to your ssh-agent. An ssh-agent is a program that securely stores your keys so that you don’t need to keep entering your passphrase. 🔍 To learn more, check out our docs about adding your SSH key to ssh-agent.  To add this new SSH key to the ssh-agent, run the following command. Note that you will need to add your passphrase when prompted. ssh-add ~/.ssh/id_ed25519 Now that you have created the SSH key and configured your ssh-agent, the next step is adding the public key to GitHub. In your terminal, run the following command. cat ~/.ssh/id_ed25519.pub Copy the entire line that appears in the terminal as a response to that command. Open a browser and navigate to github.com. Click your profile picture in the top-right corner and select Settings. In the menu on the left-hand side, select SSH and GPG keys. On the right-hand side, click the green New SSH key button. Give the key that you’re about to add a name in the “Title” box that describes this key in a way you’ll remember. For example, if this is your work laptop you might enter a title of “work-laptop”. Paste the key you copied from the terminal into the “Key” box. Click the green Add SSH key button at the bottom of the window. Congratulations! Your computer is now configured to connect to GitHub over SSH. How do I add a PAT to GitHub? What is a PAT? PAT stands for Personal Access Token. A PAT is a special credential that you create on GitHub for tools that need authentication. You control its permissions and can revoke it any time. On GitHub, you’ll commonly use a PAT to authenticate via command line or the GitHub API. There are two types of PATs available: fine-grained tokens and classic tokens. First we’ll walk through creating a fine-grained PAT. Open a browser and navigate to github.com. Click your profile picture in the top-right corner and select Settings. Scroll to the bottom of the list of options in the left-hand column and select Developer settings. In the left-hand column, expand the option for Personal access tokens. Select Fine-grained tokens from the options displayed. Click the green Generate new token button in the center of the window. Enter a name and description for the token. This should make it clear what the token is going to be used for (e.g., a name of “cli-access” with a description of “access the Copilot CLI”). Under “Expiration,” select a date that matches how long you need the token to be valid. Once the token expires, it will not work anymore. Under “Repository access,” select which repositories you want the PAT to be able to access. You can limit the selection to only specific repositories if you know which repositories it will need to access. Under “Permissions”, click Add permissions to select which permissions you’re granting to this PAT. This lets you define the scope of what the PAT can do. For each permission, you can specify whether it has read-only access or read and write access. When you’re satisfied with the permissions, scroll to the bottom and click the green Generate token button. A window pops up, providing a review of all of the information associated with this token. Verify that the information is correct, and then click Generate token. GitHub will now show you the token. Make sure that you copy it and store it in a safe location (e.g., a password manager), because GitHub only shows you this token once. 🔍 For more information, check out our documentation about Personal Access Tokens. Now let’s go through creating a classic token. As you’ll see, it’s very similar in several ways. Open a browser and navigate to github.com. Click your profile picture in the top-right corner and select Settings. Scroll to the bottom of the list of options in the left-hand column and select Developer settings. In the left-hand column, expand the option for Personal access tokens. Select Tokens (classic) from the options displayed. In the main window, click Generate new token and select Generate new token (classic).

Developers work across many surfaces like the CLI, IDE, and GitHub. The terminal is often where they turn to move fast, automate tasks, or work directly with systems and scripts. Tools like the GitHub Copilot CLI already make this easier. You can generate commands, debug issues, and move quicker without leaving the terminal. However, like any environment, the CLI can still accumulate friction: re-running the same commands, re-explaining context, or translating logs for your team into something they can act on. These small steps add up, especially when every team’s stack and standards are a little different. But what if your terminal didn’t just run commands, it understood your stack, your tools, and your team’s standards? That’s where custom agents come in. Instead of starting from scratch each time, you can encode your team’s context into reusable workflows that go beyond one-off prompts. With custom agents in the CLI, you can turn repeated tasks and patterns into consistent, reviewable workflows that fit naturally alongside your other tools, further tailoring GitHub Copilot CLI with expertise for specific development tasks. What are custom agents? A custom agent is a Copilot agent that can be defined using a Markdown file. Instead of relying on generic behavior, you describe how the agent should operate, what tools it can use, what standards it should follow, and what outputs it should produce. The result: its behavior is consistent wherever it runs. Each coding agent you create can act as a specialized agent tailored for a specific task. For example, a generic coding agent might suggest how to clean up your code. But a custom agent can apply your formatting rules, tooling, accessibility standards, review requirements, and safety requirements every time it runs. Custom agents are defined using agent profiles, or files that live directly in your repository. Written in Markdown, these agent profiles let you specify: The agent’s role and area of expertise Which tools it can access Guardrails that keep outputs safe and consistent The snippet below shows the beginning of an agent profile that acts as an expert assistant for web accessibility: — description: ‘Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing’ name: ‘Accessibility Expert’ model: GPT-4.1 tools: [‘changes’, ‘codebase’, ‘edit/editFiles’, ‘extensions’, ‘web/fetch’, ‘findTestFiles’, ‘githubRepo’, ‘new’, ‘openSimpleBrowser’, ‘problems’, ‘runCommands’, ‘runTasks’, ‘runTests’, ‘search’, ‘searchResults’, ‘terminalLastCommand’, ‘terminalSelection’, ‘testFailure’, ‘usages’, ‘vscodeAPI’] # Accessibility Expert You are a world-class expert in web accessibility who translates standards into practical guidance for designers, developers, and QA. You ensure products are inclusive, usable, and aligned with WCAG 2.1/2.2 across A/AA/AAA. # Your Expertise **Standards & Policy**: WCAG 2.1/2.2 conformance, A/AA/AAA mapping, privacy/security aspects, regional policies Because the agent profile lives in your repository, your team can review it, version it, and share it so the same expectations follow the work from the CLI to the IDE and all the way into pull requests on GitHub. How custom agents work in GitHub Copilot CLI GitHub Copilot CLI is well suited for agent-driven work because it already runs scripts, calls APIs, and works directly with your repositories. Defining agents here lets you further tailor Copilot CLI by encoding execution-heavy workflows once, then invoking it from the terminal. The agent will execute your workflow the same way every time. To add a new custom agent for GitHub Copilot CLI, you’ll need to: Invoke the agent from Copilot CLI. From the terminal, run the Copilot CLI and use the /agentslash command. Select the custom agent you want to use. Create an agent profile in the .“github“/agents directory of your target repository. The agent profile is a Markdown file with YAML frontmatter that defines the agent’s role, scope, capabilities, and guardrails, so it behaves consistently in your workflows. The agent profile file ends with .agent.md – for example, accessibility.agent.md. Because the agent profile is a file in your repository, it can be reviewed, updated, and shared. Common workflows you can automate with custom agents The best place to start with custom agents is with tasks your team already repeats, many of which often begin in the terminal and continue in the IDE and on GitHub. Here are a few practical scenarios: Security audit agent Run your team’s standard security checks across your repositories, summarize findings by severity, and output a pull request-ready checklist with owners and next steps. # .github/agents/security-audit.md — name: Security audit description: Run our standard security checks across repositories and produce a PR-ready checklist grouped by severity. tools: # Keep this list aligned with what your team actually runs in CI. – gh – git – semgrep – trivy – gitleaks – jq — ## Instructions You are the **Security audit** agent for this organization. ### Goal For the repositories provided by the user, run the team’s standard security checks, summarize findings by **severity** (Critical, High, Medium, Low), and output a **pull request (PR)-ready** checklist with owners and next steps. ### Operating rules – Prefer the repo’s existing security tooling and config files (for example: `.semgrep.yml`, `.trivyignore`, `.gitleaks.toml`) when present. – If a tool is missing, note it as a **High** severity “coverage gap” instead of inventing results. – Don’t paste secrets or full vulnerable payloads into output. Redact tokens and credentials. – Use inclusive language (use allowlist/denylist). – When referencing dates, use the format “March 23, 2026”. ### Standard checks to run (per repository) 1. Secret scanning locally: – `gitleaks detect –redact –no-git –source .` (or use the repository’s preferred invocation) 2. Container scanning (if a container image or Dockerfile exists): – `trivy fs .` 3. SAST (if semgrep config exists): – `semgrep scan –config .semgrep.yml` 4. Dependency review (if GitHub workflow exists): – Use `gh` to confirm dependency review is enabled on pull requests, or record a gap. ### Ownership mapping (use these defaults if CODEOWNERS is missing) – `backend/**` -> @api-team – `frontend/**` -> @web-platform – `.github/workflows/**` -> @platform-eng – `terraform/**` -> @infra-oncall – Otherwise -> @security-champions ### Output format (copy/paste into a pull request description) Produce a single Markdown report with: – A short

Ever watched GitHub Copilot CLI extract a JAR file to a temporary directory, grep through .class files, and piece together an API signature from raw bytecode? The agent is resourceful, but without a language server, that’s the best it can do. The Language Server Protocol (LSP) is the standard that powers go to definition, find references, and type resolution in editors like VS Code. It works just as well in the terminal. The LSP Setup skill automates the installation and configuration of LSP servers for Copilot CLI, so the agent gets precise, structured answers about your code instead of relying on text search heuristics. In this post, you’ll learn how the skill works under the hood, see the configuration format it generates, and get set up for any of the 14 languages it supports today. The problem: heuristic code understanding Without an LSP server, the agent in GitHub Copilot CLI reverse-engineers API information through text search and binary extraction. For a Java project, that might look like: # Find the dependency JAR find ~/.m2/repository -name “*httpclient*.jar” # Extract it to a temp directory mkdir /tmp/httpclient && cd /tmp/httpclient jar xf ~/.m2/repository/org/apache/httpcomponents/httpclient/4.5.14/httpclient-4.5.14.jar # Search extracted class files for a method grep -r “execute” –include=”*.class” . For Python, the agent might cat files inside site-packages. For TypeScript, it walks node_modules. These text-based approaches work for simple cases, but they’re doing pattern-matching over raw text rather than true semantic analysis, so they miss generics, overloads, and transitive types, and can’t see compiled bytecode at all. That’s exactly the gap a language server close. An LSP server solves this structurally. When the agent sends a textDocument/definition request for a symbol, the language server returns the exact source location, fully resolved type, and signature. What is an agent skill? Agent skill is a reusable instruction set that extends what an AI coding agent can do. Skills are defined in Markdown files with YAML frontmatter and follow a standard structure: trigger descriptions, step-by-step workflows, reference data, and behavioral constraints. The LSP Setup skill uses this structure to guide the agent through a multi-step installation process, detecting the operating system, choosing the right package manager, writing valid configuration, and verifying the result. How the LSP Setup skill works When triggered, the skill executes a seven-step workflow: 1. Language selection The agent uses ask_user with a set of choices to determine which language the user needs LSP support for. This drives all subsequent steps. 2. Operating system detection The agent runs uname -s (or checks $env:OS / %OS% on Windows) to determine the target platform. Install commands vary by operating system. For example, brew install jdtls on macOS versus downloading from eclipse.org on Linux. 3. LSP server lookup The skill includes a reference file (references/lsp-servers.md) with curated data for 14 languages: install commands per operating system, binary names, and ready-to-use config snippets. The agent reads this file and selects the matching entry. 4. Configuration scope The agent asks whether the config should be: User-level: ~/.copilot/lsp-config.json—applies to all repositories Repository-level: lsp.json at the repository root or .github/lsp.json—scoped to a single project Repository-level configuration takes precedence when both exist. 5. Installation The agent runs the appropriate install command. For example: # TypeScript on any OS npm install -g typescript typescript-language-server # Java on macOS brew install jdtls # Rust on any OS rustup component add rust-analyzer 6. Configuration The agent writes or merges an entry into the chosen config file. The format uses a lspServers object where each key is a server identifier: { “lspServers”: { “java”: { “command”: “jdtls”, “args”: [], “fileExtensions”: { “.java”: “java” } } } } Key rules the skill enforces: command must be on $PATH or an absolute path args typically includes “–stdio” for standard I/O transport (some servers like jdtls handle this internally) fileExtensions maps each extension (with leading dot) to a language identifier Existing entries in the config file are preserved — the agent merges, never overwrites 7. Verification The agent runs which <binary> (or where.exe on Windows) to confirm the server is accessible, then validates the config file is well-formed JSON. Supported languages The skill comes with a set of predefined language servers for several programming languages. If the coding agent faces one that it is not mapped out already, it will search for an appropriate server and walk you through manual configuration. What changes after setup Once an LSP server is configured, the CLI agent can: Resolve types across dependencies — no more grepping through JAR files or node_modules Jump to definitions in third-party libraries, even when source isn’t checked into the repository Find all references to a symbol across the project Read hover documentation for any function, class, or type This means the agent spends less time on tool calls and produces more accurate code on the first pass. For you, that’s less time waiting while the agent decompiles a JAR file or greps through node_modules to answer a question your IDE already knows, and fewer wrong turns built on a misread signature. The agent reasons about your code with the same structured understanding you get from go-to-definition in your editor, so you can hand it bigger, gnarlier tasks and trust the result. Get started Download the skill: visit the Awesome Copilot LSP Setup skill page and click the Download button to get a ZIP file. Extract the ZIP to ~/.copilot/skills/ by running: unzip lsp-setup.zip -d ~/.copilot/skills/ Restart GitHub Copilot CLI: if Copilot CLI is already running, type /exit first. Then relaunch copilot so it picks up the new skill. Ask the agent to set up a language server: for example, “set up LSP for Java” or “enable code intelligence for Python”. Verify: after the skill installs and configures the LSP server, restart Copilot CLI one more time (/exit, then relaunch), run /lsp to check the server status, and try go-to-definition on a symbol from one of your dependencies. The skill is part of the Awesome Copilot project. It’s open source, so contributions and feedback are welcome! The post

In March and April we shared updates on GitHub’s availability and infrastructure investments. As that work continues and we approach some major milestones, we wanted to start sharing more regular updates in our monthly availability reports.  So before we dive into incidents from May, here’s how we’re tracking with our ongoing work to make GitHub more reliable.   Our progress in making GitHub more resilient The short version: GitHub’s traffic is growing rapidly, driven in large part by AI-assisted and agentic development workflows, and we’ve been transforming our infrastructure to keep up with it. That means moving to Azure for elastic capacity, breaking our monolith apart into isolated services, and eliminating the shared failure points that have driven past incidents.  Here’s where we stand. We’re now serving 40% of monolith traffic from Azure (up from 8% in February), with Git traffic at 30% and repository replication at 99%. We’ve more than doubled our effective capacity in four months. At the same time, we’re completing the isolation of our primary database cluster: splitting users, authentication, and authorization into independent domains so that a problem in one can no longer cascade across the platform. Our new users service is fully cut over, and handling double the traffic at substantially lower database cost. Stateless authentication tokens are also rolling out, eliminating per-request database lookups that amplified pressure during traffic spikes.  We are making structural changes that permanently remove failure modes. We acknowledge that we have work to do, but we’re committed to getting it done and making GitHub reliable when and where you need it. The principle guiding our decision is simple: availability, then capacity, then features.  Thanks for your partnership as we keep building GitHub’s reliability and resilience.  In May, we experienced nine incidents that resulted in degraded performance across GitHub services. May 04 15:45 UTC (lasting 55 minutes) On May 4, 2026, between 15:34 and 16:40 UTC, github.com experienced a service disruption that produced elevated latency and an increased rate of request failures across a broad set of customer-facing services. Total customer impact lasted approximately one hour and six minutes.  The most significantly impacted service was pull requests, which was statused Red for the duration of peak impact. Issues, actions, webhooks, and Git operations experienced elevated latency and intermittent errors. A number of dependent services—including Codespaces, Pages, Packages, OAuth and GitHub Apps, Marketplace, and Copilot—also saw varying degrees of degraded performance due to shared data dependencies. At peak, approximately 1.3% of requests returned a 5xx response, averaging around 0.46% across the duration of the incident.  The disruption was triggered by a routine online schema migration running against a large, heavily-accessed database table. The migration had been progressing without issue for several hours, but as traffic ramped up toward the weekly peak, the combined load from the migration and normal production traffic saturated database connection capacity. This produced query contention on a primary database and cascading timeouts across services that depend on it.  The incident was detected within approximately three minutes of the first signs of impact through a combination of automated monitoring and on-call observation. Once the contributing migration was identified, it was paused, and dependent services recovered shortly thereafter. Time to mitigation was approximately 33 minutes, and full resolution followed approximately 30 minutes later  As follow-up, we are implementing several improvements to reduce the likelihood and blast radius of a similar event. Migrations against large, high-traffic tables will be more tightly aligned with low-traffic windows and will use dynamic throttling that adapts to live cluster load. We are adding automated circuit breakers that will pause in-flight migrations when latency or connection utilization on the underlying database crosses safe thresholds, and we are extending our monitoring so that migration-induced pressure (i.e., write rate, lock time, and connection saturation) triggers alerts before customer impact occurs. In parallel, we are reviewing connection-pool capacity to ensure adequate headroom is maintained while migrations are running.   May 05 13:37 UTC (lasting 3 hours and 49 minutes) May 06 07:19 UTC (lasting 2 hours and 25 minutes) On May 5 and May 6, GitHub Actions was degraded across two related incidents affecting hosted runners. The two events were connected: remediation work performed after the May 5 incident introduced the configuration issue that triggered the May 6 incident.  On May 5, 2026, from 13:22 to 17:05 UTC, GitHub Actions hosted runners in the East US region were degraded. Approximately 13.5% of jobs requesting a standard runner failed and ~16% of requested larger runners with private networking pinned to East US failed or were delayed by more than five minutes. Copilot code review requests were also impacted. Approximately 8,500 code review requests timed out during this window. Affected users saw an error comment on their pull requests and were able to retry by rerequesting a review. Most runner requests were picked up by other regions automatically, but a portion of requests still routing to East US were impacted.  This was triggered by a scale-up operation for hosted runner VMs in the East US region. This is a regular operation, but the VM create load hit an internal rate limit when VM creates pull images from storage. Existing backoff logic was not triggered because of the response code returned in this case. The rate limiting and VM creation failures were mitigated by reducing load to allow for recovery and allowing queued work to be processed. By 15:34 UTC, queued and failed job assignments were mostly mitigated, with less than 0.5% of runner assignments impacted between 15:34 and full recovery at 17:05.  On May 6, 2026, from 06:45 to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were again degraded, and approximately 17.1% of jobs requesting a standard runner failed. The issue was caused by unexpected configuration data introduced during remediation work for the previous day’s incident, which blocked new allocations as daily load ramped up. We removed the problematic data at 08:51 UTC, allowing allocations to resume and runner pools to scale back up and recover.   We are improving our system’s throttling behavior when limits occur, improving our controls to more quickly mitigate similar situations in the future, and reviewing all limits end-to-end for similar operations. In addition, we are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.  May 06 11:21 UTC (lasting 38 minutes) On May 6, 2026, between 11:02 and 11:13 UTC,

Secret scanning plays a critical role in protecting developers and organizations. It helps catch exposed credentials early and prevents small mistakes from turning into real incidents. At GitHub’s scale, even small inefficiencies create real friction. Too many false positives make alerts harder to trust. When alerts feel noisy, developers spend more time triaging and less time fixing real issues. Over time, this slows down remediation and reduces confidence in the system. To address this challenge, GitHub collaborated with Microsoft Security & AI’s Agents Offense team to bring more contextual reasoning into GitHub’s secret scanning verification. The collaboration applied the verification approach from Agentic Secret Finder, a broader detection and verification system developed to understand potential secrets in context, not just whether they match a secret-like pattern. This helped GitHub explore ways to reduce low-value alerts while preserving the coverage you expect from secret scanning. Secret scanning at GitHub today GitHub secret scanning combines pattern-based detection with AI-based detection to identify potential secrets. Pattern-based detection catches known secret formats, such as partner patterns for tokens and API keys. AI-powered generic secret detection expands coverage to unstructured secrets like passwords that don’t match a known provider pattern. GitHub already has industry-leading precision for provider-pattern secret detection at massive scale, processing billions of pushes and protecting tens of millions of developers across millions of repositories. As GitHub expanded into AI-powered secret detection, the next challenge was bringing the precision of AI-detected secrets closer to the same high standard as provider-pattern detections. This collaboration focused on combining GitHub’s large-scale detection pipeline with LLM-based contextual verification to improve alert quality and developer trust. Our approach: Make secret scanning alerts trustworthy Secret scanning is most useful when you can quickly tell which alerts need action. GitHub already has safeguards to reduce noise, but some secret-like values need more context to determine whether they represent a real exposure. To make those alerts easier to trust, we added more reasoning to the verification step. By looking at how a detected value appears in code, the system can better separate real exposures from values that only look sensitive. This helps you spend less time investigating low-value alerts and more time fixing the issues that matter. Where this fits in the pipeline This approach builds directly on the existing system. Detection continues to generate candidates, and the verification step evaluates them. More context-awareness makes this system better at distinguishing real secrets from noise. The result is higher precision without changing upstream detection logic or reducing coverage. How it works A key challenge in verification is deciding what context to provide. A small snippet of code is often not enough to determine whether something is a real secret. At the same time, passing entire files or repositories introduces too much noise and increases cost and latency. Instead of giving more context, we’re giving better context. Rather than send large amounts of code, we extract a small set of high-signal information that helps explain how the value is used. For example, we look for cases where a value is assigned to a variable and later passed into an API request, authentication header, database client, or cloud SDK call. Pattern matching can tell us that a value looks like a secret, but it can’t tell us whether the value is actually being used as one. The surrounding usage context helps the model distinguish real exposures from false alarms, such as random UUIDs or opaque strings, without reviewing the full file or repository. Focused context, not more data It’s natural to assume that improving accuracy requires analyzing more of the codebase. But the opposite is true. Most false positives can be resolved with focused, file-level context. What matters is not how much code the model sees, but whether it has the right signals. In many cases, you can determine whether a value is a real secret by looking at how it is used within a single file. Values that resemble placeholders, test data, or unused configuration can often be filtered out without deeper analysis. This keeps the system both effective and practical: high accuracy, low latency, and the ability to scale across large codebases. Results: reducing false positives in practice We evaluated this approach on hundreds of customer-confirmed false positive alerts. Our target was a 65% reduction. The result was 75.76%, exceeding that goal while maintaining strong detection performance. In practice, this means significantly less noise and a higher proportion of alerts that require action. False positive reduction results based on hundreds of customer-confirmed false positive alerts. This improvement shows up directly in the developer experience. With fewer irrelevant alerts, it becomes easier to trust what you see. Less time is spent triaging noise, and real issues can be prioritized and fixed faster. What’s next We’re continuing to evaluate this approach on larger datasets and live traffic, while improving how context is extracted and used for verification. Reducing false positives has been a consistent need at scale. This work focuses on improving signal quality where it matters most, making alerts easier to trust and act on. The goal is simple: fewer distractions, clearer signals, and faster action on real risks. Get started by running the risk assessment for your organization today, or learn more about secret scanning. The post Making secret scanning more trustworthy: Reducing false positives at scale appeared first on The GitHub Blog. ​ AI & ML, LLMs, Security, Secret Scanning The GitHub Blog

In agentic systems, more delegation isn’t always better. Imagine asking Copilot CLI to make a simple change. Instead of handling it directly, it spins up a helper agent that searches the repository, waits on a result, and stalls. Work that should have taken one step now takes three. While some tasks genuinely benefit from a specialist subagent—like exploring an unfamiliar repository, checking an independent area of the code, or running a long command while the main agent keeps moving—delegation isn’t free. Every handoff adds coordination overhead, tool calls, and wait time. If an agent delegates too eagerly, the “help” can become friction.   We recently released an improvement to our agentic harness called smarter subagent delegation. This makes Copilot CLI more selective by helping the main agent:   Stay focused when it can move faster on its own. Delegate when a specialist creates real leverage. Parallelize work when tasks are truly independent. Smarter subagent delegation has now rolled out to 100% of Copilot CLI production traffic. If you want to get started today, simply update GitHub Copilot CLI by running the /update command in your terminal to version 1.0.42 or later.  In a production A/B test, this improvement reduced tool failures per session by 23%, including a 27% reduction in search tool failures and an 18% reduction in edit tool failures. It also improved total user wait time by 5% at P95 and 3% at P75, with no quality regression. Here, P95 captures wait time near the slowest 5% of sessions, while P75 reflects wait time toward the slower end of typical sessions. This means fewer unnecessary handoffs, fewer repeated searches, fewer failure-prone tool paths, and less waiting during long-running coding tasks.  In this post, we’ll walk through how we identified unnecessary delegation in Copilot CLI, what we changed to make delegation more selective, and how we validated those changes through offline evaluation and production A/B testing. We’ll also show why those changes led to fewer failures and less waiting—and what that looks like for developers using Copilot CLI day to day.  The problem: Delegation is powerful, but not free Subagents are one of the most important capabilities in an agentic CLI. They let Copilot break down complex work, run investigations in parallel, and keep the main agent focused on coordinating the final answer. For large codebases and multi-step engineering tasks, that can be the difference between a slow linear workflow and an efficient parallel one.  But delegation introduces its own failure modes:  Unnecessary handoffs for simple tasks that the main agent could complete faster on its own.  Overuse of exploration subagents when the handoff already contains enough context. Repeated or overlapping searches across the main agent and subagents.  Sequential delegation, where the main agent waits for a subagent instead of treating delegation as an opportunity for parallel work.  Failure-prone subagent paths, including stale file paths, moved files, incorrect relative paths, and workspace mismatches.   Figure 1. Example: tool call failure by subagents while main agent is idling.  Our goal: help developers use subagents when they create leverage, avoid them when they add overhead, and parallelize work when the task genuinely benefits from independent execution.  From problem signals to shipped improvement The way we identified the problem became the way we solved it. Instead of treating agent trajectory analysis, product changes, evaluation, and rollout as separate activities, we used them as one feedback loop: observe the agent behavior, isolate the orchestration bottleneck, make a targeted change, validate it offline, measure it online, and ship only once the end-to-end workflow improved.  Figure 2. The end-to-end improvement loop: analyze, change, validate, and ship. 1. Analyze: Let LLMs identify the delegation bottleneck Instead of manually reviewing agent sessions, we used LLMs to analyze full trajectories and identify where orchestration was helping versus where it was adding overhead. That analysis surfaced a consistent pattern: subagents were sometimes being invoked for tasks that were already narrow, obvious, or fully described in the handoff.  In those cases, the subagent could spend time re-searching the repository even though the main agent already had enough context to act directly. That clarified the improvement target: keep simple discovery-and-edit tasks in the main agent, and reserve subagents for work that is broader, cross-cutting, or naturally parallelizable.  2. Change: Refine the orchestration policy After identifying the bottleneck, we used LLMs to help translate that diagnosis into a more selective orchestration policy. Copilot CLI should handle focused work directly: find a file, read it, make a targeted change, and verify it. Delegation is more useful when the work requires independent context, broad exploration, or parallel execution. In practice, that means starting with the narrowest effective path, escalating when complexity or uncertainty creates value, and stepping back down when the task becomes focused again. Subagents should be treated as a parallelism tool, not a pause button. When Copilot launches a subagent, the main agent should continue making progress on independent work rather than simply waiting for the result. When a subagent is used, the handoff should also be specific: what the user asked, what is already known, what the subagent owns, and what kind of result the main agent needs back.  3. Validate: Test offline, confirm online, then ship Before broad rollout, we validated the change with automatically generated regression cases and existing benchmarks. This helped confirm that the new delegation guidance reduced avoidable overhead without breaking cases where subagents genuinely add value.  Finally, we moved through staff and public A/B testing, then analyzed production metrics across reliability, responsiveness, subagent workload, and quality. The gains did not come primarily from making individual LLM calls faster. Instead, it reduced orchestration overhead by avoiding unnecessary subagent paths and lowering subagent workload per user.  That end-to-end process let us move from problem signal to shipped improvement while keeping the user experience stable: fewer avoidable handoffs, fewer failure-prone tool paths, and no quality regression.  Outcomes After rolling smarter subagent delegation to production traffic, we saw measurable percentage improvements across reliability and responsiveness (Table 1):  Dimension Metric Delta Reliability  Tool failures

Welcome back to GitHub Copilot CLI for Beginners! In this series (available in video and blog format), we’ll give you everything you need to get started using GitHub Copilot CLI. So far in this series, we’ve covered how to get started and when to use interactive and non-interactive modes. In this edition, we’ll learn what slash commands are, why they matter, and how to use slash commands to control GitHub Copilot efficiently. You can complete tasks like switching models, checking token usage, and resuming past sessions right from your terminal. Let’s dive in! Understanding slash commands in GitHub Copilot CLI When working in Copilot CLI, one of the most powerful concepts to learn early on is slash commands. Slash commands are built-in controls that you can access directly from the command line. Acting as your control surface within Copilot CLI, slash commands allow you to: Guide Copilot’s behavior Inspect changes Manage context Move efficiently across sessions and projects Keep permissions tidy Slash commands can be thought of as your command center for interacting with Copilot CLI. To look at all of the options available, just type / in the command line for a scrollable list of all currently supported slash commands. Let’s take a look at some of the most popular ones. Choosing the right model Different models are optimized for different kinds of work. If you want to switch models, type /model into the command line. This will display a list of available models, along with key details like: Capabilities: Some are better for quick, lightweight tasks like refactoring, while others more efficiently handle deeper reasoning such as feature planning. Availability: The list may vary depending on your plan or organization’s settings. Cost: Numbers shown on the right of each model indicate cost multiplier, helping you choose the right balance between performance and usage in relation to your plan. Choosing the right model can significantly impact both speed and results. Managing context and token usage Copilot CLI operates within a context window, which determines how much information it can “remember” during a session. If you want to check your current usage, type /context to learn how many tokens you have left, along with system usage and available buffer. If you find that you’re running low on space, you can free up space by typing /compact in the command line. This summarizes your current conversation so you can continue without having to start a new session. Copilot CLI will do this automatically when you approach the limit, but you can also do this manually if you want to transition to a new task or clean up context mid-session. If you’d rather start fresh and completely reset your environment, you can use /clear to clear the session entirely. Working across sessions If you want to resume a previous session, you can type /resume. This will bring up a list of previous sessions you’ve had, including both local and remote sessions. Entering a previous session will show you your session history, and you can pick up right where you left off. Inspecting changes As you work with Copilot to make changes to your project, it’s important to keep track of what’s changed. If you want to see what the changes are, run /diff to see recent updates. This gives you a clear view of what modifications were made during your session, so you can validate changes before moving forward. Navigating projects and directories If you want to work across repositories or directories, you don’t have to exit Copilot. You can type /cwd to change your working directory to another repository. This allows you to scope Copilot’s work to a specific part of your project and helps you stay efficient while multitasking across codebases. Managing tool permissions In the past, you might have granted Copilot CLI permission to perform actions like editing files. Say you’re switching to a repository you want to be more careful in and want to reset those permissions: you can do so by running /reset-allowed-tools. Take this with you Using these slash commands gives you even better control over Copilot CLI—and the more familiar you become with them, the more deliberate your workflow becomes. Whether you’re switching models, managing context, or navigating across projects, using slash commands in CLI gives you the tools you need to stay in control. And if you haven’t already: open up your terminal, type /, and explore! There are many more slash commands to discover. Happy coding! Looking to try GitHub Copilot CLI? Read the docs and get started today. More resources to explore: GitHub Copilot CLI for Beginners video series GitHub Copilot CLI for Beginners: Getting started with GitHub Copilot CLI GitHub Copilot CLI for Beginners: Interactive v. non-interactive mode GitHub Copilot CLI 101: How to use GitHub Copilot from the command line Best practices for GitHub Copilot CLI The post GitHub Copilot CLI for Beginners: Overview of common slash commands appeared first on The GitHub Blog. ​ AI & ML, GitHub Copilot, GitHub Copilot CLI, GitHub Copilot CLI for Beginners The GitHub Blog

Software may be written in programming languages, but human language is at the heart of developer collaboration. Developers explain how projects work in READMEs. They ask for help in issues. They review, debate, and improve code in pull requests. That collaboration often happens in English—but not always. As AI becomes a bigger part of how developers build software, multilingual developer content matters more than ever. Today, GitHub is publishing the GitHub Multilingual Repositories Dataset, a repository-level metadata dataset designed to help researchers and developers discover public GitHub repositories with evidence of non-English natural-language content. When building the dataset, we found that language distribution differs across READMEs, issues and pull requests: Korean is the most common non-English language in issue text, but only the fifth-most common in READMEs. Portuguese tops the non-English README list with more than 3 million repositories. The dataset is now available on GitHub under CC0-1.0. It follows through on a commitment we made in 2025, as part of Microsoft’s European Digital Commitments, to make multilingual data more accessible, including to open source AI developers. What’s in the dataset The GitHub Multilingual Repositories Dataset is intentionally not a dump of repository content. Instead, it is a metadata dataset that helps developers and researchers find repositories where multilingual collaboration may be happening. The dataset covers over 80 million classification rows across more than 40 million repositories. For each public repository, we provide: Language classifications of the README, the most-commented issue, and the most-commented pull request, with the first 150 characters of each used as the input sample. We exclude texts under 20 characters. Classifications for each text source, from fastText, gcld3, and lingua-py, each with a confidence score. The dataset only includes classifications with >0.5 confidence. Repository metadata: creation timestamp, disk usage, stars, forks, primary programming language, SPDX license, issue and pull request counts, and the snapshot date. We deliberately did not collapse the three classifiers into a single label. Different classifiers have different coverage and confidence calibration, especially for lower-resource languages. By exposing all three, we let you decide how strict you want to be. Want a high-precision Greek subset? Require all three classifiers to agree above some confidence threshold. Want broad recall for an exploratory study of Romance languages? One classifier may be enough. What you can build with it The dataset is designed for the kind of work that’s hard to do with general web text: Discover repositories likely to contain developer documentation or collaboration in specific languages. Study how non-English developer communities use issues, pull requests, and READMEs. Build evaluation sets for AI coding tools, doc generators, or review assistants that need to behave well across languages. Encourage decision-makers to expand language coverage for new developer tools and AI features using data-backed arguments on the rich multilingual diversity of developers. Measure representation of European and other underrepresented languages in open source. Some caveats Language identification is hard, especially in software repositories. Repository text is often short. It may include badges, templates, installation commands, code snippets, usernames, or mixed-language content. A 150-character sample may not represent the whole repository. Classifiers also vary in coverage and calibration, especially for lower-resource languages. That is why the dataset should not be treated as a ground-truth benchmark for language identification. Instead, it is designed as a transparent discovery tool. Users can inspect classifications, confidence scores, and sources, then choose the precision and recall tradeoffs that fit their own research or development workflow. The dataset also should not be used to infer sensitive attributes about repository owners, contributors, or communities. The signals are repository-level metadata, not person-level attributes. Why open multilingual data matters Today, many European languages remain underrepresented in the online text used to build and evaluate AI systems. That creates a risk that AI tools work well for some developers, languages, and communities, while leaving others behind. Open data can help close that gap. We built this dataset because developer content is different from general web text. READMEs, issues, and pull requests contain the language of software collaboration: installation instructions, bug reports, feature requests, review comments, and community norms. That context can help build AI systems that better understand how developers actually work. By making multilingual developer-content signals easier to find and analyze, this dataset gives researchers, open source developers, and model builders another tool for studying language representation in software development. It can help identify gaps, support better evaluation, and inform more inclusive AI tools for developers across Europe and beyond. It also reflects a broader principle: Building AI for developers should include the communities, languages, and workflows developers actually use. What’s next We’ll be discussing the dataset, and the broader importance of open data for multilingual AI, at the Open Innovation Dialogue Hub in Strasbourg on June 16. The event is co-organized by the Microsoft Open Innovation Center, the Council of Europe, and GitHub, and will bring together policymakers, researchers, cultural institutions, and open innovation leaders to discuss AI, linguistic diversity, cultural heritage, and open data. Multilingual AI needs multilingual developer communities. We hope this dataset helps more people study, support, and build for them. By releasing it under CC0-1.0 on GitHub, we’re inviting researchers, open source maintainers, and model builders to use it, critique it, extend it, and build evaluation sets and tools on top of it. If you do something interesting with it, we’d love to hear about it. The post Accelerating researchers and developers building multilingual AI with a new open dataset appeared first on The GitHub Blog. ​ AI & ML, LLMs The GitHub Blog

It seems like the latest hotness in git these days is the concept of worktrees. Which… is kind of funny because they’ve been around since 2015. But, nevertheless, they are cool, and you might be wondering why you’d use them, how they differ from branches, and why they are suddenly so popular. Let’s talk about it! Context switching with branches and stashing Let’s say you lived in a worktree-less world, and were working on a ticket, and suddenly an urgent bug came to you and you had to switch contexts. First, you might stash your work: git stash “wip feature login” Then you’d switch to your main branch and update: git checkout main git pull origin main Then make a bugfix branch: git checkout -b hotfix-bug Then you’d fix everything, commit, and push the branch: git add . git commit -m “fix broken submit button” git push origin hotfix-bug Then after merging a pull request, you might return back to your computer and pull main and remove the bug branch: git checkout main git pull origin main git branch -d hotfix-bug And then you could go back to the feature you were working on: git checkout feature-login git stash pop Phew. Where were we? The mental overhead of switching around, reloading files, reinstalling node_modules based on whatever changed, and so on, is a lot. The context switching burden is heavy. Now, this is a basic example, but sometimes developers would work around this kind of chaos with doing some more complicated git stash commands, or even multiple clones of the same repo (I’m guilty of that one). Until… worktrees! Context switching with worktrees With worktrees, you never leave your branch and you never stash, and your editor context for your original feature stays untouched. git worktree add ../hotfix-workspace -b hotfix-bug main This instantly creates a sibling folder called hotfix-workspace, and bases it on main, and checks out a new branch called hotfix-bug. Now you can open that folder in a new editor window (or cd into it) and fix the bug. Your original editor window stays exactly as you left it. cd ../hotfix-workspace # …fix fix fix… git add . git commit -m “fix broken submit button” git push origin hotfix-bug You merge the pull request online just like before, and once it’s merged, you can simply delete the temporary folder. cd ../main-project git worktree remove ../hotfix-workspace This is so much smoother! Worktrees can go beyond the git command line, too. For example, VS Code has full worktree support built in. You have options! And no matter where you work, worktrees give you zero risk of stash conflicts, there’s no editor disruption, and you can truly work in parallel. So… why now? For a really long time, worktrees were relatively unknown. Most developers had never heard of them, because either Git GUIs didn’t support them (or treated them as second-class citizens), or because they just usually followed the known pattern of feature branch, then work, then PR, then merge, then repeat. Now, our work as developers has changed. AI has made us work in parallel more than we ever have before in the history of software development. Developers run so many sessions in parallel, and “code review culture” is growing beyond “code writing culture.” Agents and humans can do more in parallel with worktrees. It’s the default mode for the GitHub Copilot app, and for many other modern tools. What’s the catch? Worktrees do solve a whole lot of issues, but there’s definitely some things to watch out for. Dependency bloat: each worktree folder requires its own copy of your project dependencies. If you’re running npm install or pip install across multiple of them, your computer might get very full, very quickly. Folder management: you have to delete the worktree folders, to avoid cluttering your parent directory over time. Apps like the GitHub Copilot app do often handle this for you, but it’s still something you might have to do yourself if you’re operating in the terminal yourself. Global .gitignore requirements: if you create worktree folders inside your main repo directory, you have to manually add them to .gitignore to not accidentally track them. You can make these worktrees outside of your main repo (and many apps do that by default), but it’s worth noting. One branch limits: Git prevents you from checking out the exact same branch in two different worktrees at the same time to prevent data corruption. How do I use worktrees in the GitHub Copilot app? Great question! What’s awesome is they “just work” out of the box. When you open the app, there’s a dropdown that asks you where you want to run your new session on the home screen. The default is a new worktree. Then, once you kick off a new session, you can click the session name at the top of the app, and you’ll see the (fun!) generated name of your worktree, as well as the path where it’s located, the project that worktree is for, and details about the changes that you’ve made. Easy peasy lemon squeezy! Should I use worktrees? I will give you the most senior developer answer I can: It depends! You might prefer working in one way or another. You might not do as much work in parallel and like the mental model of branches and stashing. You might only do worktrees from now on. You might want to do both! The world’s your oyster, and you can try them all in the GitHub Copilot app today. The post What are git worktrees, and why should I use them? appeared first on The GitHub Blog. ​ AI & ML, Git, GitHub Copilot, git worktrees, GitHub Copilot app The GitHub Blog

As Copilot takes on more agentic work, from planning and editing to debugging, reviewing, and calling tools across longer sessions, efficiency means more than using fewer tokens. It means being smarter about how you use them. Increasing efficiency starts with reducing what Copilot has to repeat from turn to turn, including context, tool definitions, and cached state. It continues with choosing the right model for the job. A quick explanation, a focused edit, and a complex multi-file change should not all be treated the same way. We are working on both: improving the Copilot harness so more of each session goes toward the task itself, and expanding Auto so Copilot can pick the model that fits the work without asking developers to make that choice every time. This post focuses on harness improvements in GitHub Copilot for VS Code and on ongoing work to expand Auto across Copilot surfaces. Increased prompt caching and deferred tools In longer GitHub Copilot sessions in VS Code, the harness prepares a lot of recurring information for the model: instructions, repository context, conversation history, available tools, and the current state of the task. Some of that context is needed. Some of it can be cached, deferred, or loaded only when it becomes relevant. Two improvements in GitHub Copilot for VS Code are doing most of the work here. Prompt caching helps Copilot reuse model state for repeated prompt prefixes instead of recomputing the same prefix on every request. Tool search lets the model load tool definitions on demand, instead of sending every full tool schema into context on every turn. That matters more as agents use more tools. A session may need access to MCP tools, terminal commands, file operations, workspace search, and product-specific actions. Loading every full tool definition up front adds fixed cost to each turn, even when only a small number of tools are relevant to the task. With tool search, Copilot can keep the available toolset broad while sending less unnecessary tool schema into the model. For a deeper technical look at the implementation, including prompt caching, cache-control breakpoints, provider-specific tool search, and how these changes work across long-running agentic sessions, read the VS Code technical deep dive. Where GitHub Copilot auto model selection fits in Auto answers a practical question: which model is the best fit for this task right now? After your first prompt, Copilot uses task intent and current model health to choose a model that best fits the task. Different kinds of work, like quick explanations, focused edits, or multi-file changes, do not all benefit from the same level of reasoning, so Auto makes that call without requiring you to tune model settings. In our evaluations, no single model consistently performed best across tasks. In many cases, a more efficient model reached the same outcome, while stronger models mattered most when the task required deeper reasoning. Auto learns where stronger reasoning improves the result. It routes up when the task demands it and stays more efficient when it does not. The goal is not to trade quality for cost, but to use the model that best fits the work. How Auto selects the right model Auto combines two signals: what model is healthy and available right now, and what kind of work Copilot is being asked to do. Real-time model health: a dynamic engine tracks model availability, utilization, speed, error rates, and cost. A model may be capable of handling a task, but that does not mean it is the best choice at that moment. Auto takes current system conditions into account so Copilot can route to a model that is both capable and ready to respond. Task-aware routing with HyDRA: a routing model that considers factors like reasoning depth, code complexity, debugging difficulty, and tool orchestration needs. HyDRA identifies models that can meet the quality bar for the task, then chooses the best fit among them. Figure 1: Three HyDRA operating points illustrate tunability: (Peak) exceeds Sonnet at 12.9% savings; (Agg.) balances quality for 72.5% savings. Figure 2: HyDRA (Cons.) ties OpenRouter Auto on resolution rate (70.8%) at 3.3x the savings. HyDRA (Agg.) outperforms both Azure Foundry operating modes. Taken together, these signals let Auto avoid a one-size-fits-all approach. The point is not to send every task to the biggest model, or every task to the cheapest one. It is to choose the model that fits the work. Making Auto work in practice Getting routing right in evaluations is only part of the problem. To make Auto useful in real workflows, we also had to account for how developers actually use Copilot: conversations get longer, context builds up, tasks shift, and developers work in many languages. Cache-aware routing. Switching models on every turn may sound flexible, but it can work against efficiency. When a conversation stays on the same model, the prompt prefix can be cached and reused across turns. Switching models mid-conversation breaks that cache, which can cost more than the routing change saves. Auto avoids that by routing at natural cache boundaries: on the first turn, when there is no cache to lose, and after compaction, when Copilot summarizes older turns and the prompt prefix resets. Between those points, the selected model stays in place so the cache can keep building. Routing across languages. Copilot serves developers around the world, so routing has to work in languages other than English. We trained the routing model on conversations across 16 language families, including CJK, European, and others. In evaluations, routing accuracy stayed within four points of the English baseline across language groups, with no statistically significant quality gap. Figure 3: Intelligent routing stays within 4 points of English baseline. Model evaluations across English, European, CJK, and other script families, based on a held out evaluation set sampled from production VS Code chat telemetry across 19 languages. Learning when escalation matters. Instead of labeling tasks as simply “easy” or “hard,” we trained the router to learn where models actually diverge. For each training query, responses

For students and young professionals who refuse to settle, meet the most accessible XPS ever built.   ​  ​For students and young professionals who refuse to settle, meet the most accessible XPS ever built. Laptops Blog | Dell