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.
| Billing answers every page in a few round trips, not forty: its reads run together, Stripe is asked at most hourly, and the ledger has a time index | 1 | -- What happened to an issue or a pull request, told in its conversation: |
| 2 | -- who was assigned, whose review was asked for, when it was closed. These | |
| 3 | -- sit among the comments in the order they happened. | |
| 4 | -- kind is 'comment' or 'event'. | |
| 5 | ALTER TABLE comments ADD COLUMN kind TEXT NOT NULL DEFAULT 'comment'; | |
| 6 | ||
| 7 | -- The people a pull request is assigned to, and those whose review was | |
| 8 | -- asked for: JSON arrays of usernames. `g1t-agent` among the reviewers | |
| 9 | -- means a g1t agent was asked. | |
| 10 | ALTER TABLE pulls ADD COLUMN assignees TEXT NOT NULL DEFAULT '[]'; | |
| 11 | ALTER TABLE pulls ADD COLUMN reviewers TEXT NOT NULL DEFAULT '[]'; |
This file's history is long; its oldest lines are credited to the oldest commit read.