Source Code Control Events

Source Code Control events includes the subjects and predicates related to changes in Source Code repositories that are relevant from a Continuous Delivery perspective.

Subjects

This specification defines three subjects in this stage: repository, branch, and change. Events associated with these subjects are triggered by actions performed by software developers or bots that provide useful automation for software developers.

Subject	Description	Predicates
repository	A software configuration management (SCM)repository	created, modified, deleted
branch	A branch in a software configuration management (SCM)repository	created, deleted
change	A change proposed to the content of a repository	created, reviewed, merged, abandoned, updated

Each repository can emit events related with proposed source code changes. Each change can include a single or multiple commits that can also be tracked.

repository

An SCM repository is identified by a name, an owner which can be a user or an organization, a url which is where the repository is hosted and optionally a viewUrl, which is a web location for humans to browse the content of the repository.

Field	Type	Description	Examples
id	String	See id	an-org/a-repo, an-user/a-repo
source	URI-Reference	See source	my-git.example
name	String	The name of the repository	spec, community, a-repo
owner	String	The owner of the repository	cdevents, an-org, an-user
url	URI	URL to the repository for API operations. This URL needs to include the protocol used to connect to the repository.	git://my-git.example/an-org/a-repo
viewUrl	URI	URL for humans to view the content of the repository	https://my-git.example/an-org/a-repo/view

branch

A branch in an SCM repository is identified by its id.

Field	Type	Description	Examples
id	String	See id	main, feature-a, fix-issue-1
source	URI-Reference	See source	my-git.example
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

change

A change identifies a proposed set of changes to the content of a repository. The usual lifecycle of a change The data model for changes is not defined yet.

Field	Type	Description	Examples
id	String	See id	1234, featureBranch123
source	URI-Reference	See source	my-git.example
description	String	Description associated with the change, e.g. A pull request's description	This PR addresses a fix for some feature
repository	Object (repository)	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

Events

repository created

A new Source Code Repository was created to host source code for a project.

• Event Type: dev.cdevents.repository.created.0.3.0
• Predicate: created
• Subject: repository

Field	Type	Description	Examples	Required
id	String	See id	an-org/a-repo, an-user/a-repo, repo123	✅
source	URI-Reference	See source	my-git.example
name	String	The name of the repository	spec, community, a-repo	✅
owner	String	The owner of the repository	cdevents, an-org, an-user
url	URI	URL to the repository	git://my-git.example/an-org/a-repo	✅
viewUrl	URI	URL for humans to view the content of the repository	https://my-git.example/an-org/a-repo/view

repository modified

A Source Code Repository modified some of its attributes, like location, or owner.

• Event Type: dev.cdevents.repository.modified.0.3.0
• Predicate: modified
• Subject: repository

Field	Type	Description	Examples	Required
id	String	See id	an-org/a-repo, an-user/a-repo, repo123	✅
source	URI-Reference	See source	my-git.example
name	String	The name of the repository	spec, community, a-repo	✅
owner	String	The owner of the repository	cdevents, an-org, an-user
url	URI	URL to the repository	git://my-git.example/an-org/a-repo	✅
viewUrl	URI	URL for humans to view the content of the repository	https://my-git.example/an-org/a-repo/view

repository deleted

• Event Type: dev.cdevents.repository.deleted.0.3.0
• Predicate: modified
• Subject: repository

Field	Type	Description	Examples	Required
id	String	See id	an-org/a-repo, an-user/a-repo, repo123	✅
source	URI-Reference	See source	my-git.example
name	String	The name of the repository	spec, community, a-repo
owner	String	The owner of the repository	cdevents, an-org, an-user
url	URI	URL to the repository	git://my-git.example/an-org/a-repo
viewUrl	URI	URL for humans to view the content of the repository	https://my-git.example/an-org/a-repo/view

branch created

A branch inside the Repository was created.

• Event Type: dev.cdevents.branch.created.0.3.0
• Predicate: created
• Subject: branch

Field	Type	Description	Examples	Required
id	String	See id	main, feature-a, fix-issue-1	✅
source	URI-Reference	See source	my-git.example/an-org/a-repo
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

branch deleted

A branch inside the Repository was deleted.

• Event Type: dev.cdevents.branch.deleted.0.3.0
• Predicate: deleted
• Subject: branch

Field	Type	Description	Examples	Required
id	String	See id	main, feature-a, fix-issue-1	✅
source	URI-Reference	See source	my-git.example/an-org/a-rep
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

change created

A source code change was created and submitted to a repository specific branch. Examples: PullRequest sent to Github, MergeRequest sent to Gitlab, Change created in Gerrit.

• Event Type: dev.cdevents.change.created.0.4.0
• Predicate: created
• Subject: change

Field	Type	Description	Examples	Required
id	String	See id	1234, featureBranch123	✅
source	URI-Reference	See source	my-git.example/an-org/a-repo
description	String	Description associated with the change, e.g. A pull request's description	This PR addresses a fix for some feature
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

change reviewed

Someone (user) or an automated system submitted an review to the source code change. A user or an automated system needs to be in charge of understanding how many approvals/rejections are needed for this change to be merged or rejected. The review event needs to include if the change is approved by the reviewer, more changes are needed or if the change is rejected.

• Event Type: dev.cdevents.change.reviewed.0.3.0
• Predicate: reviewed
• Subject: change

Field	Type	Description	Examples	Required
id	String	See id	1234, featureBranch123	✅
source	URI-Reference	See source	my-git.example/an-org/a-repo
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

change merged

A change is merged to the target branch where it was submitted.

• Event Type: dev.cdevents.change.merged.0.3.0
• Predicate: merged
• Subject: change

Field	Type	Description	Examples	Required
id	String	See id	1234, featureBranch123, 1a429d2f06fa49d8ece5045ac6471dc8a2276895	✅
source	URI-Reference	See source	my-git.example/an-org/a-repo
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

change abandoned

A tool or a user decides that the change has been inactive for a while and it can be considered abandoned.

• Event Type: dev.cdevents.change.abandoned.0.3.0
• Predicate: abandoned
• Subject: change

Field	Type	Description	Examples	Required
id	String	See id	1234, featureBranch123	✅
source	URI-Reference	See source	my-git.example/an-org/a-repo
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}

change updated

A Change has been updated, for example a new commit is added or removed from an existing Change.

• Event Type: dev.cdevents.change.updated.0.3.0
• Predicate: updated
• Subject: change

Field	Type	Description	Examples	Required
id	String	See id	1234, featureBranch123	✅
source	URI-Reference	See source	my-git.example/an-org/a-repo
repository	Object	A reference to the repository where the change event happened	{"id": "an-org/a-repo"}