github-issue-query

To query GitHub issues and filter JSON output, use a shell script leveraging the GitHub CLI (gh) with optional jq expressions to transform and format the resulting data. This method returns schema information when no jq is provided and full data when jq is supplied.

Yes, you need both the GitHub CLI (gh) and jq installed to query issues with custom filters. The gh CLI retrieves the structured JSON output from the repository, while jq applies the in-line filters and projections to transform the results.

When you query GitHub issues without providing a jq expression, the script returns a schema overview plus the data size. This allows you to gauge the result scope and understand the available fields before applying targeted jq-based filtering.

Yes, you can query GitHub issues from a specific owner/repo instead of the current repository. The script supports querying the current repository by default or allowing you to specify a different owner/repo to retrieve issues with common filters like state, labels, and assignees.

The best way to reduce noise when retrieving large sets of GitHub issues is by applying jq-based filters to the gh CLI output. This enables targeted data views and powerful in-line projections, returning only the specific fields and issues you need.