Version

repository.* events

The lifecycle of a project's repositories: registration, edits, disconnecting, reconnecting and deletion.

The lifecycle of a project's repositories: registration, edits, disconnecting, reconnecting and deletion. A repository is where a project's code lives and where branches, commits and pull requests will be read from once Git hosting is connected, so a pipeline, a mirror of the registry or a deployment tool subscribes to this family to follow which repositories are in use.

Every event in the family is scoped to the project, so project_id in the envelope is always set and an endpoint confined to one project receives only that project's events. The payloads are thin on purpose: the ids, the full name and what the transition itself carries, never a snapshot of the repository. Read the repositories endpoint for the record.

Background

Required ability

Tokens subscribing to repository.* events need repository:view at mint time.

Events

How is this guide?

Last updated on

Version

On this page

What changed recentlyEvery release of Zuse Bifrost, with the pages it touched.

For AI agents: llms.txt ยท llms-full.txt