Skip to content

Extend default discover_tickets_command to include GitHub Issues #14

@Neokil

Description

@Neokil

Problem

The default discover_tickets_command only fetches tickets from Shortcut. Users who track work in GitHub Issues — or who use both — get no results from GitHub out of the box. They can write a custom command themselves, but there's no default that covers this common case.

The discover_tickets_command mechanism itself is already tool-agnostic; the gap is in the default implementation.

Solution

Update the default discover_tickets_command script to also fetch open GitHub Issues. The list of repositories to query should be defined as a clearly visible variable at the top of the script so users can easily adjust it without understanding the rest of the command:

# GitHub repositories to include in ticket discovery (owner/repo format).
# Add or remove entries to match the repos you want to track.
GITHUB_REPOS=(
  "Neokil/AutoPR"
)

The script then calls gh issue list for each repo and merges the results with the Shortcut output, normalised to the same schema the Discover panel already expects.

If gh is not installed or not authenticated, GitHub results are silently omitted — the command still succeeds with whatever sources are available.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions