g1t/services/work/migrations/0023_read_paths.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.
| Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily | 1 | -- Reading a pull request without asking the repos service anything. |
| 2 | -- | |
| 3 | -- Whether the branch a pull request would land on has commits it does not, | |
| 4 | -- worked out with its mergeability on every push to either side | |
| 5 | -- (mergeability.rs) and kept beside `mergeable_key`, the pair of commits | |
| 6 | -- it is for. Showing a pull request reads it from here; until a push | |
| 7 | -- fills it in, the repos service is asked as before. 1 or 0; NULL until | |
| 8 | -- first worked out. | |
| 9 | ALTER TABLE pulls ADD COLUMN behind INTEGER; | |
| 10 | ||
| 11 | -- An agent's unanswered questions and handoffs, by the pull request that | |
| 12 | -- sent them (confidence.rs): found directly instead of by reading every | |
| 13 | -- message in the repository. | |
| 14 | CREATE INDEX IF NOT EXISTS agent_messages_by_sender ON agent_messages (repo_id, from_number); |