g1t/services/work/migrations/0014_mergeability.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 and memory, checks and conflicts, profiles, slug renames, custom domains | 1 | -- Whether a pull request merges cleanly into the branch it targets, worked |
| 2 | -- out ahead of time whenever its head or that branch moves, as GitHub's | |
| 3 | -- mergeability: first by comparing the files each side changed, and where | |
| 4 | -- they share some, by a short probe in a sandbox. | |
| 5 | -- | |
| 6 | -- mergeable: clean, conflicting, checking, or NULL for not known. | |
| 7 | ALTER TABLE pulls ADD COLUMN mergeable TEXT; | |
| 8 | -- JSON array of the paths that conflict, when conflicting. | |
| 9 | ALTER TABLE pulls ADD COLUMN conflicts TEXT; | |
| 10 | -- "<head>..<base>": the pair of commits the answer is for, so each pair is | |
| 11 | -- worked out once. | |
| 12 | ALTER TABLE pulls ADD COLUMN mergeable_key TEXT; | |
| 13 | -- The probe under way: its token's hash, and when it is given up on. | |
| 14 | ALTER TABLE pulls ADD COLUMN mergeable_token_hash TEXT; | |
| 15 | ALTER TABLE pulls ADD COLUMN mergeable_until TEXT; |