g1t/services/work/migrations/0004_up_to_date.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 | -- Whether a pull request must contain the default branch's latest commits |
| 2 | -- before it may merge. Off unless a repository turns it on, as on GitHub. | |
| 3 | ALTER TABLE repo_settings ADD COLUMN require_up_to_date INTEGER NOT NULL DEFAULT 0; | |
| 4 | ||
| 5 | -- A merge that was asked for while the pull request was behind. g1t brings | |
| 6 | -- it up to date and then lands it. JSON: who asked, and whether the issue | |
| 7 | -- stays open. The time bounds how long the request stands. | |
| 8 | ALTER TABLE pulls ADD COLUMN land_requested TEXT; | |
| 9 | ALTER TABLE pulls ADD COLUMN land_requested_at TEXT; |