Skip to content

issue-tracker 0.3.0: Sync this table to GitHub (#177 item 14) - #276

Merged
michielbdejong merged 3 commits into
mainfrom
claude/issue-tracker-sync-existing-table
Oct 2, 2026
Merged

michielbdejong merged 3 commits into
mainfrom
claude/issue-tracker-sync-existing-table

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

On an issue-v1 table the GitHub issues app didn't make, it now offers Sync this table to GitHub (#177 §6.2 item 14), following calendar 0.3.0 (#272). It:

  • asks for the host's "Allow editing" (requestRowAccess) when the row grant doesn't cover the App's row-extras;
  • keeps a binding under the App (synced-table, the repository, sync state and a comments folder) and never writes the table itself;
  • runs the same sync as on the app's own table: compare on open, review before send, the same conflict rules, bookkeeping on the rows;
  • leaves existing rows local until "Publish to GitHub" (Q6);
  • never deletes a row ("Remove from board" isn't offered there);
  • pauses with "Allow editing again" when the grant lapses.

Two related changes:

  • The App now renders issue-v1 and declares its row extras from the first open, so "+ Add view" offers it before a repository is bound.
  • Atomic's localId joins the row extras, because the Bridge sets it on imported rows.

Release: bundle 160,628 bytes, limit 173 KiB. Catalog entry 0.3.0, still enabled: false. Usertest is usertest-7.

Tests:

  • Unit: app/syncTable.test.ts (12 tests, against a fake host that enforces the pinned grant scope), plus view tests.
  • E2E: hand-made table → Add view → Sync this table → Allow editing → connect → choose a repository → import → a status edit sent after review.

Checks: issue-tracker unit (236) and e2e (2/2, run twice). Also: tooling tests 251/251, apps and ontology checks, certify, e2e tsc, oxlint (0 errors) and oxfmt.

Part of #177 (item 14 for issue-tracker).

🤖 Generated with Claude Code

michielbdejong and others added 3 commits October 2, 2026 15:37
On an issue-v1 table the app didn't make, the app offers "Sync this table
to GitHub": it asks for the host's "Allow editing" when the row grant
doesn't cover its row-extras, keeps a binding under the App
(synced-table, repository, sync state, comments folder), and then syncs
that table as its own: compare on open, review before send, the same
conflict rules, bookkeeping on the rows. Existing rows stay local until
Publish to GitHub, rows are never deleted, the table is never written,
and a lapsed grant pauses the sync.

The App now renders issue-v1 and declares its row extras from the first
open, and Atomic's localId joins the row extras (the Bridge sets it on
imported rows).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	integrations/README.md
@gitguardian

gitguardian Bot commented Oct 2, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
37816143 Triggered Generic High Entropy Secret 543db78 integrations/timesheets/live/fakeClockify.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant