Sync open GitHub issues into the project backlog - #254
Merged
Merged
Conversation
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
1 participant
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.
The project Backlog now includes its open GitHub issues alongside local tasks. Issues sync through the desktop's existing
ghlogin on board entry, focus, every minute while visible, and manual refresh. Fetching follows every page and excludes pull requests; a failed refresh keeps the last successful result for the current engine session and shows an error.Selecting an issue shows its description and opens the existing task composer with its title, URL, and body. Created tasks persist the source issue URL, disappear from the issue list, and retain their work when GitHub closes the issue. Concurrent starts on one engine return the same task without launching another agent. Task routing preserves the selected local or remote environment; older boxes explicitly reject the new creation method with update guidance (protocol v11).
Validation: all workspace typechecks; 493 tests passing; 51 focused tests passing after the final database-index change. Verified against live GitHub data in the real Electron dev app, including composer prefilling, refresh, project switching, and the unchanged blank New task flow.