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
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.
Introducing Agent HQ: Any agent, any way you work
At Universe 2025, GitHub’s next evolution introduces a single, unified workflow for developers to be able to orchestrate any agent, any time, anywhere.
Octoverse: A new developer joins GitHub every second as AI leads TypeScript to #1
In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.