Repository navigation
feat: route Linear and GitHub issues by agent assignment - #55
Draft
maxigimenez wants to merge 1 commit into
Draft
maxigimenez wants to merge 1 commit into
maxigimenez wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Assigning a Linear or GitHub issue to a configured Hermes bot can now start an implementation run, with explicit repository context and the existing summary posted back to the source issue.
This is iteration 1 of the six-PR plan in
docs/plans/assigned-ticket-pr-feedback.md. It includes scoped Linear identities, paginated issue/PR intake, validated assignment templates, CLI configuration and diagnostics, dashboard setup/editing, and additive migration008_linear_agent_identity.sql.Current assignment is eligible even on first observation or after downtime. Closed/completed issues, wrong workspaces, missing repositories, and ambiguous agent mappings cannot start assigned implementation. Existing profile-targeted configurations remain valid, including profiles sharing a GitHub account. Once-only dispatch suppresses repeated implementation after item updates.
Validation:
Release gate still pending: live initial assignment and source-summary checks in disposable Linear/GitHub targets with the actual Hermes profile, plus the Node 22/24 CI matrix. This PR remains draft until those gates pass.
Deploy the API/migration before the updated dashboard and runner; upgrade the designated runner before enabling assignment routes. Use one runner per watched project/profile. Disable new routes to roll back intake and explicitly reconcile any active runs; keep the additive columns.
Verified PR/evidence tracking, durable reporting and automatic same-session PR feedback are later iterations. This release uses the existing best-effort summary path. No production deployment or bot exercise has been performed.