main · last commit
6 hours ago ·
ti41arbu
sr-ht-dolt-03v Deeper rename: repo/repository -> database across the service
Lined Up
bd update sr-ht-dolt-03v --claim
bd close sr-ht-dolt-03v
| Created by | Eugene Blikh |
| Owner | bigbes@gmail.com |
| Created | 2026-08-18T09:20:59Z |
| Updated | 2026-08-18T09:20:59Z |
The token grant scope is now dolt.sr.ht/DATABASES (sr-ht-dolt-xic), and the user-facing surface has always said 'database' — the GraphQL databases connection, the web pages, the docs. The layers underneath still say repo: ~1300 identifier occurrences across Go (RepoDiskPath, GetRepoByOwnerAndName, ListReposForViewer, ReposRoot, ...) plus the schema itself (CREATE TABLE repository, access.repo_id, uq_access_user_id_repo_id in schema.sql / migrations/0001_initial.sql). Doing it properly means a data migration on top of the Go rename, so it was deliberately left out of the scope-name fix rather than half-done. Decide whether it is worth it at all: the split is defensible as-is (a Dolt database IS a repository at the storage layer, which is what remotesapi talks to), and the cost is a migration on live data.
If taken: rename Go identifiers first in one mechanical pass, then the columns behind a migration, keeping the SQL rename last so a rollback is a schema-only revert.
No outgoing dependencies.
Nothing depends on this issue.
| id | sr-ht-dolt-03v |
| content_hash | 67d1a84e865ba3ac15599e384da2bdc3a52fe17c1f0c68f8d8ff11de5f0613e9 |
| title | Deeper rename: repo/repository -> database across the service |
| description | The token grant scope is now dolt.sr.ht/DATABASES (sr-ht-dolt-xic), and the user-facing surface has always said 'database' — the GraphQL databases connection, the web pages, the docs. The layers underneath still say repo: ~1300 identifier occurrences across Go (RepoDiskPath, GetRepoByOwnerAndName, ListReposForViewer, ReposRoot, ...) plus the schema itself (CREATE TABLE repository, access.repo_id, uq_access_user_id_repo_id in schema.sql / migrations/0001_initial.sql). Doing it properly means a data migration on top of the Go rename, so it was deliberately left out of the scope-name fix rather than half-done. Decide whether it is worth it at all: the split is defensible as-is (a Dolt database IS a repository at the storage layer, which is what remotesapi talks to), and the cost is a migration on live data. |
| design | If taken: rename Go identifiers first in one mechanical pass, then the columns behind a migration, keeping the SQL rename last so a rollback is a schema-only revert. |
| acceptance_criteria | |
| notes | |
| status | open |
| priority | 3 |
| issue_type | task |
| assignee | NULL |
| estimated_minutes | NULL |
| created_at | 2026-08-18T09:20:59Z |
| created_by | Eugene Blikh |
| owner | bigbes@gmail.com |
| updated_at | 2026-08-18T09:20:59Z |
| closed_at | NULL |
| closed_by_session | |
| external_ref | NULL |
| spec_id | |
| compaction_level | 0 |
| compacted_at | NULL |
| compacted_at_commit | NULL |
| original_size | NULL |
| sender | |
| ephemeral | 0 |
| wisp_type | |
| pinned | 0 |
| is_template | 0 |
| mol_type | |
| work_type | |
| source_system | |
| metadata | �{} |
| source_repo | |
| close_reason | |
| event_kind | |
| actor | |
| target | |
| payload | |
| await_type | |
| await_id | |
| timeout_ns | 0 |
| waiters | |
| hook_bead | |
| role_bead | |
| agent_state | |
| last_activity | NULL |
| role_type | |
| rig | |
| due_at | NULL |
| defer_until | NULL |
| no_history | 0 |
| started_at | NULL |
| is_blocked | 0 |
| id | 01a0142c-8b8f-7b17-a61b-7368a34fbd04 |
| issue_id | sr-ht-dolt-03v |
| event_type | created |
| actor | Eugene Blikh |
| old_value | |
| new_value | |
| comment | NULL |
| created_at | 2026-08-18T12:20:58Z |
No comments.