g1t/services/work/migrations/0003_repo_settings.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 | -- How a repository wants its pull requests handled. One row per repository |
| 2 | -- that has changed a setting; a missing row means the defaults. | |
| 3 | CREATE TABLE repo_settings ( | |
| 4 | repo_id TEXT PRIMARY KEY, | |
| 5 | -- Land a g1t agent's pull request without a person once it is ready: | |
| 6 | -- checks passed, approved by the reviewing agent, up to date. | |
| 7 | auto_merge INTEGER NOT NULL DEFAULT 0, | |
| 8 | -- Username of the member who last changed the settings. | |
| 9 | updated_by TEXT NOT NULL, | |
| 10 | updated_at TEXT NOT NULL | |
| 11 | ); |