pulls/pr_01m47d24b0e6n91zwymwxg0vpx

public

22 lines1,174 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.

Agents as a team: lifecycle, merge queue, billing and a new shell3d ago	1	-- What g1t needs to see a pull request made by its own agent through to
	2	-- ready-to-merge without anyone pressing a button: checks, review,
	3	-- revision, catching up.
	4
	5	-- What the reviewing agent decided: approve or request_changes. NULL when
	6	-- the review could not be written.
	7	ALTER TABLE review_runs ADD COLUMN verdict TEXT;
	8
	9	-- Set on a pull request a g1t agent opens from now on. Ones made before
	10	-- this existed are left alone, so nothing starts on them unasked.
	11	ALTER TABLE pulls ADD COLUMN managed INTEGER NOT NULL DEFAULT 0;
	12	-- How many times the agent has been sent back to revise, and when last.
	13	-- A review from before the last revision no longer counts.
	14	ALTER TABLE pulls ADD COLUMN revisions INTEGER NOT NULL DEFAULT 0;
	15	ALTER TABLE pulls ADD COLUMN revised_at TEXT;
	16	-- The step under way (review, revision or catch_up) and when to stop
	17	-- waiting for it. Claiming a step sets these in one statement, so a step
	18	-- is taken once. A push to the pull request clears them.
	19	ALTER TABLE pulls ADD COLUMN working_on TEXT;
	20	ALTER TABLE pulls ADD COLUMN working_until TEXT;
	21	-- Why g1t stopped and is asking a person, if it has.
	22	ALTER TABLE pulls ADD COLUMN stalled TEXT;