pr_01m47d15m3e54sn21z27rpy5n9/services/work/migrations/0014_mergeability.sql

15 lines817 bytesCodeBlame
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.
7ALTER TABLE pulls ADD COLUMN mergeable TEXT;
8-- JSON array of the paths that conflict, when conflicting.
9ALTER 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.
12ALTER TABLE pulls ADD COLUMN mergeable_key TEXT;
13-- The probe under way: its token's hash, and when it is given up on.
14ALTER TABLE pulls ADD COLUMN mergeable_token_hash TEXT;
15ALTER TABLE pulls ADD COLUMN mergeable_until TEXT;