GitHub now records who pushed every commit, so a repository's history names the account that made the change.
Operations · FinanceGitHub began recording the authenticated user who pushed each commit on October 12, 2026, and shows that identity in the UI and API next to the author and committer fields (changelog). It comes with one new ruleset condition, Committer must match pusher, which blocks a push when the committer does not match a verified email of the account that pushed it (changelog). The purpose is an audit trail that a person with write access cannot sign with someone else's name.
The feature is in limited public preview for GitHub Enterprise customers, and access is requested through the account team (changelog, checked October 13, 2026). GitHub gives no date for general availability and no price (changelog). Push rulesets apply to private and internal repositories and their fork networks (docs).
More businesses now keep records and rules as plain files in a repository: a vault per domain for the item master, price rules, supplier terms and brand vocabulary. In that setup the commit history is the record of who changed a cost and when. Until now, that record rested on names the pushing client typed in. Using pusher identity in production will require Enterprise preview access, one account per person and per agent, and a dashboard that reads the pusher rather than the author.
An identity the client cannot set
GitHub states the problem plainly: author and committer fields are "just strings that the pushing client supplies" (changelog). Anyone with write access can set them to any name and email (changelog). GitHub already authenticated the push itself, and it now attaches that authenticated account to every commit in it (changelog).
The same week, GitHub let Enterprise admins tie Copilot agent activity, including MCP tool calls, to a named user through telemetry.capture.identity, with prompt and output capture off by default (changelog). Together, the commit says which account pushed a change and the telemetry says whose agent session produced it. This is the same pattern as an approval stamp on a purchase order: the signature counts only if it cannot be copied.
Two teams whose records carry money
The fit is any repository where several people or agents can change a record that moves money.
Operations
Planners and product developers edit the item master, lead times and reorder rules, and agents increasingly push those edits for them. Give each agent its own GitHub account, such as a machine user, so its pushes never appear under a person's name. A team running Grok Bot should note that a Team Bot's plugins sign in with the account of whoever is talking to it (docs). The pusher field then shows which person's session made the change. The dashboard that lists recent changes to a style should read that field.
Finance
Landed-cost rules, duty rates, payment terms and margin targets belong in a repository where every change has a name a controller can trust. Turn on Committer must match pusher for that repository first. During close, the controller reviews the month's commits to the rules folder by pusher, not by author. Any change that lacks a matching approval in the pull request goes back to its owner.
A rollout limited to the records that move money
Each step narrows the rule to the repositories where a forged name would cost the most.
- List the repositories that hold finance rules, pricing and supplier terms, and name an owner for each.
- Request preview access from the GitHub account team.
- Create a separate account for every agent or bot that pushes, and remove shared credentials.
- Add a push ruleset with
Committer must match pusherto one repository, and watch blocked pushes for a week. - Update the change dashboard to show the pusher next to the author.
- Extend the ruleset to the remaining repositories on the list.
- Turn on Copilot identity capture only if Copilot is the agent in use, and leave content capture off.
Where the preview stops
- The preview is limited to GitHub Enterprise customers by request (changelog). A single-owner vault gains little from it.
- GitHub does not publish the API field names or the UI locations in the announcement (changelog). Dashboards may need changes once they are documented.
- Pusher identity names the account, not the person behind a shared login. Shared tokens defeat it.
- GitHub warns that Copilot content capture can include source code, file contents and paths (changelog).
A repository's history was only as honest as the names typed into it, and the records that carry money were the ones most exposed. The steps above give every person and agent its own account, enforce the match on finance and pricing repositories first, and point the change dashboard at the pusher. For the full documentation, see GitHub's guide to push rulesets.
Sources
- GitHub — Push attribution for commits, limited public preview (October 12, 2026)
- GitHub — Client telemetry user attribution and configurable capture (October 12, 2026)
- GitHub Docs — About rulesets: push rulesets (checked October 13, 2026)
- xAI — Grok Bot docs: Team Bots (checked October 13, 2026)