Test working on an issue in a different repo
See original GitHub issueRefs: https://github.com/microsoft/vscode-pull-request-github/issues/2820
- anyOS @Tyriar
- anyOS @stuartleeks (windows)
Complexity: 3
There are no restrictions in the “Issues” view that require that your queries only include the repo you currently have open. For example, my queries are the following:
{
"githubIssues.queries": [
{
"label": "Recovery",
"query": "assignee:alexr00 is:open repo:microsoft/vscode repo:microsoft/vscode-remote-release repo:microsoft/vscode-pull-request-github sort:updated-desc label:candidate"
},
{
"label": "Remote",
"query": "assignee:alexr00 is:open repo:microsoft/vscode-remote-release sort:updated-desc milestone:\"July 2021\""
},
{
"label": "Code",
"query": "assignee:alexr00 is:open repo:microsoft/vscode sort:updated-desc milestone:\"July 2021\""
},
{
"label": "Issues",
"query": "assignee:alexr00 is:open repo:microsoft/vscode-pull-request-github sort:updated-desc milestone:\"July 2021\""
},
],
}
Previously, if I had Microsoft/vscode open, but wanted to start working on an issue from my “Remote” query above, I would get a modal dialog saying that there isn’t a matching repo so I couldn’t start working on the issue. Now, this should just work.
Setup:
- Install the Nightly build of GitHub Pull Requests and Issues. Disable the stable build of the extension if you have it.
- Set your issues queries setting to some queries that return issues that are outside of the folder you have open.
- To start working on an issue, open the “Issues” view and use the “Start working” action on an issue.
Verify:
- That you can start working on an issue that isn’t in the repo you have open when you only have one folder open.
- That you can start working on an issue that isn’t in the repo you have open when you have a multiroot workspace with multiple repos. Verify that you get prompted to pick a repo.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Separate or project repository to store tests? Which, why, and ...
While starting to work with end-to-end tests, one of the first questions is where to store them. Alongside source code or in separate...
Read more >Should You Keep End-To-End Tests in the Same Repo or Not?
Having a separate repo has its set up benefits. Overall, it keeps the overall development and testing environment cleaner.
Read more >You Can Overcome The Test Repo Dilemma. Now. - QE Unit
We have two possible choices for each situation encountered. The first is to maintain our tests with the code of our application within...
Read more >How to test 2 linked repos? (#999) · Issues - gitlab-runner
For me this is a situation where I want to run two different types of tests: Unit tests and other tests that can...
Read more >One repo or separate repos? - SQA Stack Exchange
So far the best argument for single-repository design is that we can run all tests at once from one repo. There is no...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I have released a new nightly build so this should be good to test now.
Working for me on
v2021.7.37985😄