New and Improved Service Hook Payloads
The service hook payloads now have the following new fields: distinct=true for commits that are new to the repository created=true for new branches deleted=true for branch deletions base=NAME for the…
The service hook payloads now have the following new fields:
-
distinct=truefor commits that are new to the repository -
created=truefor new branches -
deleted=truefor branch deletions -
base=NAMEfor the base ref associated with a new branch
The campfire service hook now uses these new fields to improve messages sent to campfire:
Merges
Before, merges would replay existing commits that were merged into the branch:

Now, these distinct=false commits are ignored so only new commits show up:

This means that clean fast-forward merges no longer produce any campfire activity.
Forced Pushes
![]()
New Branches
New branches created via git push origin base:new show the name of the base branch:
![]()
Branches created locally with commits show what’s new:

Deleted Branches
![]()
Note: Service hooks were not previously fired on branch deletions. CI and other endpoints that do not care about branch deletions can ignore deleted=true payloads.
Written by
Related posts
The future of AI-powered software optimization (and how it can help your team)
We envision the future of AI-enabled tooling to look like near-effortless engineering for sustainability. We call it Continuous Efficiency.
Let’s talk about GitHub Actions
A look at how we rebuilt GitHub Actions’ core architecture and shipped long-requested upgrades to improve performance, workflow flexibility, reliability, and everyday developer experience.
GitHub Availability Report: November 2025
In November, we experienced three incidents that resulted in degraded performance across GitHub services.