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.
| An issue being worked on no longer offers Bring your own agent beside the pull request doing it | 1 | -- Deleting a workspace is soft. Its row stays, with when, by whom and |
| 2 | -- until when it can be restored, and every read that resolves a workspace | |
| 3 | -- leaves it out: nobody's memberships list it, its tokens are refused and | |
| 4 | -- its pages are not found. Its members and tokens are kept as they were, so | |
| 5 | -- a restore by g1t's staff brings it back whole. The row holding its slug | |
| 6 | -- keeps the slug from anyone else meanwhile. Once purge_after passes, the | |
| 7 | -- scheduled purge removes it as deleting always did (src/deletion.rs). | |
| 8 | -- | |
| 9 | -- `deleted_went` is what went with it, counted when it was deleted (JSON: | |
| 10 | -- repositories, projects, members), for staff deciding on a restore. | |
| 11 | -- | |
| 12 | -- `protected`: a workspace that can never be deleted, by anyone. It is | |
| 13 | -- kept on the row as well as in PROTECTED_WORKSPACES, so a rename does not | |
| 14 | -- take the protection away. | |
| 15 | ALTER TABLE workspaces ADD COLUMN deleted_at TEXT; | |
| 16 | ALTER TABLE workspaces ADD COLUMN deleted_by TEXT; | |
| 17 | ALTER TABLE workspaces ADD COLUMN purge_after TEXT; | |
| 18 | ALTER TABLE workspaces ADD COLUMN deleted_went TEXT; | |
| 19 | ALTER TABLE workspaces ADD COLUMN protected INTEGER NOT NULL DEFAULT 0; | |
| 20 | ||
| 21 | CREATE INDEX IF NOT EXISTS workspaces_purge_after ON workspaces (purge_after) WHERE deleted_at IS NOT NULL; | |
| 22 | ||
| 23 | -- Flagon's workspace runs g1t. | |
| 24 | UPDATE workspaces SET protected = 1 WHERE slug = 'flagon-io'; |
This file's history is long; its oldest lines are credited to the oldest commit read.