💡 Repository name now included in the outgoing webhook when a build is finished

Changelog Website
, ,
1

:new_button: What’s new

We added repository_name to outgoing webhook payloads for build events. Its value is org/repo (for example, repo-owner/repo-slug), derived from the app’s connected repository URL.

:puzzle_piece: Why this matters

It was hard to tell which repository a build belonged to without making extra api calls to Bitrise. This is particularly useful for large organisations. Many teams only had the build url/slug in the payload and avoided additional lookups due to rate limits, performance, or simplicity. Having the repository baked into the event lets you route, filter, and correlate builds immediately.

:light_bulb: Example payload
Here is a representative example of the new field in the payload:

{
  "build_slug": "7aa5abf6-00c1-46a2-937e-ee574a6b184x",
  "build_number": 312679,
  "app_slug": "46b6b9a78a418ee8",
  "repository_name": "repo-owner/repo-slug",
  "build_status": 0,
  "build_triggered_workflow": "ci-workflow",
  "url": "https://app.bitrise.io/build/7aa5abf6-00c1-46a2-937e-ee574a6b184x",
  "git": {
    "provider": "github-app",
    "src_branch": "best-feature-ever",
    "dst_branch": "master",
    "pull_request_id": 12345,
    "tag": null,
    "commit_hash": "2e11b002e200177d10af12589627e11f4e89d416"
  }
}

:guide_dog: Setup

  • No changes needed if you already consume outgoing webhooks. the new field appears automatically.
  • To start using it, parse repository_name from the incoming payload and apply your routing/filtering rules.