Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine GitHub Query Hierarchy with Subtree nodes (for ex. Milestones, Labels, Repositories) #5511

Closed
maddes8cht opened this issue Nov 26, 2023 · 1 comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@maddes8cht
Copy link

In the GitHub Issues.querys section, I've noticed that the "default" query displays all open issues of the current repository assigned to me, organized by milestones as tree nodes. While attempting to recreate this structure with custom queries, I encountered challenges, specifically in having subtrees under the tree node corresponding to the "label" assigned to the query.

For instance, I want to access closed issues using:

"githubIssues.queries": [
    {
        "label": "My Issues",
        "query": "default"
    },
    {
        "label": "Closed Issues",
        "query": "-state:open author:${user} repo:${owner}/${repository}"
    }
]

However, this setup doesn't provide subnodes with milestones.

Additionally, I would like to review my other open issues across different repositories:

{
    "label": "Other Open Issues",
    "query": "state:open author:${user} sort:updated-desc -repo:${owner}/${repository}"
}

It would be ideal to have these issues ordered in subtrees by their repository names.

Is it currently possible to configure such a structure in VSCode? If not, I propose it as a valuable feature to enhance the usability and flexibility of the GitHub Pull Requests and Issues extension.

Your guidance on achieving this structure or consideration for implementing it as a feature would be greatly appreciated.

@alexr00
Copy link
Member

alexr00 commented Nov 29, 2023

Duplicate of #1881

@alexr00 alexr00 marked this as a duplicate of #1881 Nov 29, 2023
@alexr00 alexr00 closed this as completed Nov 29, 2023
@alexr00 alexr00 added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants