flagon-io/g1t

public

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

g1t/services/work/migrations/0013_commit_statuses.sql

15 lines526 bytesCode Blame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

GitHub Actions on g1t, part two: running workflows3d ago	1	-- Statuses on commits: what a workflow run (or another tool) says about a
	2	-- commit. A pull request whose head has a status that is pending or failed
	3	-- waits, or is sent back, as for its acceptance checks.
	4	CREATE TABLE commit_statuses (
	5	repo_id TEXT NOT NULL,
	6	sha TEXT NOT NULL,
	7	-- What reported it, such as "CI / push".
	8	context TEXT NOT NULL,
	9	-- pending, success, failure or error.
	10	state TEXT NOT NULL,
	11	description TEXT,
	12	target_url TEXT,
	13	updated_at TEXT NOT NULL,
	14	PRIMARY KEY (repo_id, sha, context)
	15	);