Backups: restore the records, and carry release assets issue #175 closed: completed andymccall opened this 21 days ago · 0 comments

docs/backups.md §7. A restore brought back stores and repository rows only; issues, proposals and the rest stayed in the run's records, and release assets (under /assets, outside the stores) were never sent.

• Records carry _names: the account, organisation and team names behind the ids their rows point at.
• Restore: the repository row with its settings, then every table parents first with ids mapped, accounts found by name (a missing one blanked where allowed, the row left out where not, and said), webhook secrets named to be entered again, search rebuilt.
• Release assets sent once each as blobs and written back checked against their hash.
• Test: a fresh hub that lacks one of the accounts gets the issue, comment, label, milestone, assignee, proposal, review, events, release and asset back.