Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GS: Refresh history, repair, and unlink workflows

Open
#404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
full-stack

Research direction

Start with docs/design/google-sheets/failure-recovery.md, spreadsheet-layout.md, and sharing-security.md, then review parent #398 and dependencies #400, #401, and #402. Implement and verify the listed refresh history, diagnostics, repair, unlink, and managed-sheet removal behaviors, including safe audit records, preserved exported data, and no automatic destination mutation.

Written by the indexing model from the issue text.

Description

cool feature

Parent: #398
Depends on: #400, #401, #402

Design:

  • docs/design/google-sheets/failure-recovery.md
  • docs/design/google-sheets/spreadsheet-layout.md
  • docs/design/google-sheets/sharing-security.md

Scope

Add refresh audit history, normalized diagnostics, broken-link indicators, repair actions, copied-spreadsheet handling, unlink, and managed-sheet removal.

Acceptance criteria

  • Successful and failed refreshes append safe audit records with mode, phase, counts, duration, identities, and normalized error category.
  • Tokens, credentials, and sensitive parameters never enter audit rows.
  • UI exposes last status and refresh history per binding.
  • Repair supports deleted managed sheets, stale staging, renamed resources, copied spreadsheets, Google reauthorization, source rebinding, and checkpoint reset through explicit full refresh.
  • Repair never guesses resource identity from sheet names.
  • Unlink disables future refresh and removes refresh metadata while preserving exported data by default.
  • Removing managed worksheets is a separate destructive action.
  • SQL Browser does not delete the entire spreadsheet.
  • Broken bindings remain diagnosable and do not mutate destination data automatically.

Non-goals

Strict distributed locking, automatic repair, or Google file deletion.

Dominant language
TypeScript
Stars
8
Forks
2
Avg merge
1h 34m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Altinity/altinity-sql-browser

All issues in Altinity/altinity-sql-browser

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.