Configure Azure Pipelines app in ghe.com

I recently helped a client migrate from Azure DevOps to GitHub Enterprise Managed Users with Data Residency (ghe.com for short). And as part of the migration we rewired the exiting Azure Pipelines fro...

jessehouwing.net

Incorrect vss-extension.json not caught by tfx, nor marketplace not Azure DevOps · Issue #542 · microsoft/tfs-cli

When an extension declares 2 contributions, say vsts-msbuild-helper-task-v0 and vsts-msbuild-helper-task-v1 and each of these point to a task.json that has the same name and id, but 2 different maj...

github.com

skills/plugins/dotnet-test at main · jessehouwing/skills

Repository for skills to assist AI coding agents with .NET and C# - jessehouwing/skills

github.com

Auto-assign GitHub Copilot AI Credit budget to users

The deadline for GitHub Copilot Usage Based Billing is approaching rapidly. And today I've been busy setting up automation to assign each user their own bucket of Copilot AIC budget. On June 1st, all...

jessehouwing.net

Measuring the Value of AI

The honeymoon is over. After months of aggressive rollouts, enterprises across the globe have given their employees access to AI coding assistants, copilots, and chat interfaces. And now the inevitabl...

jessehouwing.net

The why for Usage Based Billing for GitHub Copilot

Last month GitHub announced Usage Based Billing for GitHub Copilot. This completely changes the way its costs are calculated. A lot has already been written about the impact and a lot is still unknown. In this post I want to explore the reasons why this switch was inevitable and how it enables new scenarios to make Copilot perform better than it did before. ## Quick recap of copilots current pricing model GitHub Copilot is currently available in 5 different plans: * GitHub Copilot Free - severely rate limited free version with no option to buy additional requests. * GitHub Copilot Pro - Individual license with limited Premium Request Units. * GitHub Copilot Pro+ - Individual license with more extensive Premium Request Units. * GitHub Copilot for Business - License for organizations with centralized policies and limited Premium Request Units. * GitHub Copilot Enterprise - License for organizations with centralized policies and more extensive Premium Request Units. Each of these licenses has a fixed monthly price. GitHub Copilot includes suggestions and a limited set of free models. And about a year ago, GitHub introduced the concept of Premium Request Units to pay for more powerful models and and PRUs are the used to charge for specific features like the Cloud Coding Agent and Copilot Code Review. When the Cloud Coding Agent was introduced, it could use more than 1 PRU per request. This made the cost of the agent unpredictable and GitHub soon changed the price of the Cloud Coding Agent to a single PRU per request. When a user has exhausted their included PRU budget, additional PRUs are charged. Additional PRUs have a fixed cost. ## Usages of PRUs The primary use of PRUs are to charge the costs of requests to the users of GitHub Copilot. Each model is assigned a multiplier of 0, 1, up to 50 (highest so far) PRUs. The model multiplier wasn't just used to charge the cost, it's an open secret that it was also used to divert users to other models to load balance them. Most people are more hesitant to use expensive models carelessly. The introduction of the "Auto" mode rests on this principle. Users get a 10% discount on PRUs if they let GitHub select their model. While most users seem to assume this will route them to the "best model for the task", this generally sends the request to the "model with the best availability". Premium Request Units were also reduced for promotional purposes. When Claude Opus 4.7 was introduced, it's multiplier was temporarily set to 3x, later increased to 15x. This promotional use isn't just to get us "hooked" on the more powerful model features, it's also to allow GitHub to get crucial statistics on how these new models perform and to help them iron out bugs. ## How GitHub pays for model usage The model providers, Anthropic, Google, OpenAI, X, don't charge the cost of their models in Premium Request Units. They charge the cost in terms of Tokens. Input Tokens, Output tokens and Cached tokens at the highest level. Given the amount GitHub uses, they have probably got a really good deal. But GitHub needs to balance the cost for the Tokens it spends against what it can charge its users in Premium Request Units. GitHub also balances the costs between Tokens and PRUs by limiting the maximum token window for models. For example, if you're using Claude Opus 4.6 through GitHub Copilot, the maximum token window is 200k tokens. If you use the same model directly through Anthropic you have a maximum of 1m tokens. As Agent Mode and Cloud Coding Agent got more powerful, more tools appeared, the models are using more and more tokens for every request, reducing the available token window for your requests. ## Other ways GitHub control costs GitHub has a few other options to control the maximum number of tokens you can use for each Premium Request Unit they charge you. **Agent Mode -** Agent Mode spends tokens and action minutes. GitHub can control the token spend by forcing the agent to come to an early conclusion or to postpone work to a future session. **Cloud Coding Agent** - The cloud coding agent spends tokens and action minutes. GitHub can control the token spend by forcing the agent to come to an early conclusion or to postpone work to a future session. The workflows running the Cloud Coding Agent runs on is limited to 2 hours. **Code Review** - Similar to the Cloud Coding Agent, when using GitHub's Code Review feature, GitHub can control the token spend by limiting the total time and the total of tokens the feature can spend. When using these features, GitHub can also control which model is used to perform these tasks. Some features, like tool optimization in Visual Studio Code also limit the total number of tokens used for each session by default. ## Recent creative uses New features, like subagent and fleets have multiplied the number of tokens you can use in a single Agent request. Visual Studio Code extensions have allowed users to steer the agent without completing the Agent request. These creative usages, some people might call them abuse, have allowed some people to use significantly more tokens costs than the PRU is worth. In some cases thousands time more. And instead of figuring out how to charge its users in Premium Request Units in this new model, GitHub will charge us for the actual tokens instead. ## So what changes Instead of the abstract thing, called Premium Request Units, acting as a proxy for the real cost of AI usage, we're going to be charged in tokens, the same unit in which GitHub is charged. Unfortunately, the different model providers, each charge different prices for different kinds of tokens. So GitHub still uses a multiplier so they can charge a single unit for the bill. GitHub explains how the new pricing model works on the GitHub Blog. You can see find the upcoming changes to the model multiplier in the GitHub docs. The new multipliers should not just result in higher costs, but is also expected to more equally spread the load across the available models as users will be more likely to try to find the most cost effective model to use for the work they're trying to accomplish. ## Additional changes for Business accounts In addition to the new pricing, GitHub is introducing a number of welcome changes for business accounts (Copilot for Business and Copilot Enterprise). **Pooled usage** - Under the current model, when a user has spent all of its budget, additional requests are automatically charged. Under the new model, the budget of all users is pooled together. So the unused budget from less frequent users can be consumed by more frequent users in the same organization. Only when the full pooled budget is used up, will additional usage be charged. **Individual additional budgets** - Under the current model, additional charges can be controlled through budgets, these are pooled together for all users in the same cost center. In the new model it's possible to set a per-user budget as well as a universal budget for all users in addition to the already existing budget control options. In addition to these changes, existing policy options to control costs are still available: **Enterprise, Organization** and **Cost Center Budgets** - Existing budget options to limit the total spend at the Enterprise, Organization and Cost Center can still be configured to limit the total spend on AI costs. **Limit model availability** - Enterprise and Organization level policies allow admins to control the available models. This can remove less effective and more expensive model options. **Limit feature availability** - Enterprise and Organization level policies allow admins to control the available features. This can remove more expensive features like Code Review and Cloud Coding Agent for specific users. But, ultimately, limiting the cost isn't the path forward. Optimizing the value delivered through AI is. Use these limits to bridge the time it takes to educate your users.

jessehouwing.net

The why for Usage Based Billing for GitHub Copilot

Last month GitHub announced Usage Based Billing for GitHub Copilot. This completely changes the way its costs are calculated. A lot has already been written about the impact and a lot is still unknown...

jessehouwing.net

Securing your GitHub Actions workflows to Enhance JavaScript Security | Snyk

Snyk provides a pre-built custom Snyk GitHub Actions workflow that you can add to your CI and saves you the trouble of managing the vulnerability scans using the Snyk CLI directly.

snyk.io

Github Copilot now available with Data Residency in the EU

With the current political climate there has quite a bit of buzz around Data Residency and Data Sovereignty. And the number of inquiries to migrate from GitHub Enterprise Cloud to the Data Resident version have gone up. One of the gaps in GitHub with Data Residency, was that all Copilot data could still leave the region. This is now a thing of the past: Copilot data residency in US + EU and FedRAMP compliance now available - GitHub ChangelogGitHub Copilot now supports data residency for US and EU regions, ensuring all inference processing and associated data stay within your designated geography. For US government customers, all model hosts…The GitHub BlogAllison To make use of this new feature, you must already be using the Data Resident version of GitHub Enterprise Cloud (also known as `ghe.com` or by GitHub's internal codename Proxima). To restrict Copilot to only use Data Resident models, a policy must be enabled at the Enterprise or Organization level: Set ****Restrict Copilot to Data Residency Models**** to ****Enabled everywhere**** to ensure copilot data is processed in your Data Residency region. Currently all **Generally available** copilot features are included according to GitHub, but new features may take a bit longer to be enabled on your GitHub environment, as they may not yet be available for Data Residency during preview phases. This has been the case with other GitHub features as well, so this shouldn't come as a surprise.

jessehouwing.net

Github Copilot now available with Data Residency in the EU

With the current political climate there has quite a bit of buzz around Data Residency and Data Sovereignty. One of the gaps in GitHub with Data Residency, was that all Copilot data could still leave ...

jessehouwing.net

GitHub Actions learnings from the recent nx hack

You may have seen recent reporting around the compromise of the nx project. A malicious version of their package was published to npmjs which subsequently published GitHub tokens, crypto wallets and o...

jessehouwing.net

GitHub Copilot will start training on your interactions

GitHub Copilot will start training on your data... You've probably seen this on your LinkedIn timeline in the past few days. Probably with alarming notes that this can't be controlled and that there i...

jessehouwing.net

Introducing Azure DevOps Marketplace tasks and actions: A Complete Rebuild for Speed, Stability, and Security

Introducing the Azdo marketplace project. Azure Pipelines tasks and GitHub Actions for publishing to the Azure DevOps marketplace.

jessehouwing.net

Deleted Extension Names Are No Longer Reusable · microsoft vsmarketplace · Discussion #1708

We’re updating the Visual Studio Marketplace policy regarding extension names. Effective mid-March, extension names that have been deleted will not be available for reuse, including by the original...

github.com

Keep your examples in sync with your Action

Last month I added a few more GitHub Actions to the Marketplace and while working on them found that it was easy to forget to update my examples as the implementation of the Action evolved

jessehouwing.net

Actions Example Checker - GitHub Marketplace

Validate examples in documentation against action.yml schemas

github.com

GitHub - jessehouwing/azdo-marketplace: Pipeline tasks for Azure DevOps Extensions

Pipeline tasks for Azure DevOps Extensions. Contribute to jessehouwing/azdo-marketplace development by creating an account on GitHub.

github.com

Battling Hallucinations By Paying More

My theory: improving LLM output always requires a higher token count and, therefore, cost.

matthijsvdveer.substack.com

Automatic versioning for GitHub Actions authors

As a maintainer of 3 GitHub Actions, I've always struggled a bit with the versioning of them. GitHub's documentation provides guidance, but no easy way to verify you did everything right. Based on a ...

jessehouwing.net

Automatic versioning for GitHub Actions authors

As a maintainer of 3 GitHub Actions, I've always struggled a bit with the versioning of them. GitHub's documentation provides guidance, but no easy way to verify you did everything right. Based on a ...

jessehouwing.net