pr_01m47d24b0e6n91zwymwxg0vpx/services/work/migrations/0006_merge_rules.sql
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 shell | 1 | -- More of how a repository wants its pull requests handled. |
| 2 | ||
| 3 | -- How many approving reviews a pull request needs before it may merge, and | |
| 4 | -- whether a g1t agent's approval counts as one. | |
| 5 | ALTER TABLE repo_settings ADD COLUMN required_approvals INTEGER NOT NULL DEFAULT 0; | |
| 6 | ALTER TABLE repo_settings ADD COLUMN count_agent_approvals INTEGER NOT NULL DEFAULT 1; | |
| 7 | -- Whether a member may merge although the acceptance checks did not pass. | |
| 8 | ALTER TABLE repo_settings ADD COLUMN allow_ignoring_checks INTEGER NOT NULL DEFAULT 1; | |
| 9 | -- Whether a g1t agent's pull request is reviewed by a second agent, and how | |
| 10 | -- many times its author may be sent back before a person is asked. | |
| 11 | ALTER TABLE repo_settings ADD COLUMN agent_review INTEGER NOT NULL DEFAULT 1; | |
| 12 | ALTER TABLE repo_settings ADD COLUMN max_revisions INTEGER NOT NULL DEFAULT 2; |