Repository navigation
issue-tracker 0.2.0: rows of the shared issue-v1 class (#177 item 6) - #254
Merged
3 commits merged intoOct 2, 2026
Merged
3 commits merged into
3 commits merged into
Conversation
The GitHub issues drive app now syncs into the shared class issue-v1, at
its published GitHub Pages subject:
- Rows are issue-v1: title in name, task/v1 body and status (the task/v1
tags todo, doing, blocked, done). Shared fields are read by subject
through ontology-kit's resolver only. On first open the app adds
issue-v1 to its App's renders, declares its row extras (issue number,
GitHub source, sync baseline) as row-extras, and sets its own table's
classtype to issue-v1. Shown on an Issue table it did not make, it only
shows a notice ("Sync this table" is item 14, not built).
- Blocked is the GitHub label atomic:blocked, like atomic:doing (#177 Q8):
lens, GitHubPort, the tracker actions and the sandbox plugin (plugin.js
rebuilt, manifest fixture updated). Board and list get a Blocked column;
keys 1-4.
- A status that is not exactly one of the four tags no longer fails the
pass: the row is shown with its status as it is and keeps the status it
last agreed with GitHub for the sync.
- Local-only rows (#177 Q6, this plugin's choice): a row with no GitHub
issue is left alone until "Publish to GitHub" in its panel; the create is
then held for review as before. Cards made with the app's own New issue
form are published at once (still reviewed).
- Baselines live on the rows as github-sync-baseline (#177 decision 7), not
in github-sync-state: written with every row the Bridge writes, written
at a checkpoint when they changed otherwise, read back into the Bridge's
records when a row is read. The snapshot's identity graph stays in the
sync state.
- An update over a 0.1.x install rewrites its rows in place once (own
Status tags to task/v1 tags, description to task/v1 body, isA to
issue-v1) and keeps the sync state, so unsent edits are still offered.
e2e: installs 0.2.0 from the catalog, checks the table and rows are
issue-v1 and the App renders it, publishes a row added outside the app,
and moves it to Blocked, all against the mock proxy; beforeAll checks Pages
serves issue-v1 (ontology-kit/served.mjs, copied byte-identical from the
money branch, #252). App 0.2.0 (usertest-6); catalog entry stays
enabled: false; size limit 167 KiB (measured 154,931 bytes).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nnection' into m-iv1 # Conflicts: # integrations/READINESS.md # usertest/catalog.mjs
michielbdejong
changed the base branch from
claude/issue-tracker-existing-connection
to
main
October 2, 2026 09:20
Member
|
Trekmeester (for Joep): included in batch #265 with Michiel's other PRs from 1 Oct. Its |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
issue-tracker 0.2.0: rows of the shared issue-v1 class (#177 item 6)
The GitHub issues drive app now syncs into the shared class issue-v1, at
its published GitHub Pages subject:
tags todo, doing, blocked, done). Shared fields are read by subject
through ontology-kit's resolver only. On first open the app adds
issue-v1 to its App's renders, declares its row extras (issue number,
GitHub source, sync baseline) as row-extras, and sets its own table's
classtype to issue-v1. Shown on an Issue table it did not make, it only
shows a notice ("Sync this table" is item 14, not built).
lens, GitHubPort, the tracker actions and the sandbox plugin (plugin.js
rebuilt, manifest fixture updated). Board and list get a Blocked column;
keys 1-4.
pass: the row is shown with its status as it is and keeps the status it
last agreed with GitHub for the sync.
issue is left alone until "Publish to GitHub" in its panel; the create is
then held for review as before. Cards made with the app's own New issue
form are published at once (still reviewed).
in github-sync-state: written with every row the Bridge writes, written
at a checkpoint when they changed otherwise, read back into the Bridge's
records when a row is read. The snapshot's identity graph stays in the
sync state.
Status tags to task/v1 tags, description to task/v1 body, isA to
issue-v1) and keeps the sync state, so unsent edits are still offered.
e2e: installs 0.2.0 from the catalog, checks the table and rows are
issue-v1 and the App renders it, publishes a row added outside the app,
and moves it to Blocked, all against the mock proxy; beforeAll checks Pages
serves issue-v1 (ontology-kit/served.mjs, copied byte-identical from the
money branch, #252). App 0.2.0 (usertest-6); catalog entry stays
enabled: false; size limit 167 KiB (measured 154,931 bytes).
Stacked on #249: merge that first.
Checks: issue-tracker unit (221 passed, 8 skipped) and e2e (passed twice, under one lock). Also: tooling tests 248/248, apps and ontology checks, certify, e2e and app tsc, oxlint (0 errors) and oxfmt.
Not verified:
atomic:doing/atomic:blockedlabels must exist first. The README says to create them.Part of #177 (item 6); doesn't close it.
🤖 Generated with Claude Code