No GPR panel in SCM view
See original GitHub issue- Extension version: 0.1.6
- VS Code version: Code - OSS 1.27.1 (5944e81f3c46a3938a82c701f96d7a59b074cfdc, 2018-09-06T17:56:24+03:00)
- OS version: Linux x64 4.18.5-90.current
Steps to Reproduce:
- Install Github Pull Requests
- Reload VSCode
- Go to SCM View
I’ve checked all issues related, but nothing repairs my problem. I work on a private repository with SSH. I’ve also tested with this repository, but same problem.
Here’s the origin’s URLs of the repository (I remove the owner and the repository’s name) :
git remote -v
origin git@github.com:<owner>/<repo> (fetch)
origin git@github.com:<owner>/<repo> (push)
and for the second test :
git remote -v
origin git@github.com:RobinBuschmann/sequelize-typescript.git (fetch)
origin git@github.com:RobinBuschmann/sequelize-typescript.git (push)
Github Pull Requests output :
Looking for git repository
> git symbolic-ref --short HEAD
> git rev-parse develop
> git rev-parse --symbolic-full-name develop@{u}
> git rev-list --left-right develop...refs/remotes/origin/develop
> git for-each-ref --format %(refname) %(objectname) --sort -committerdate
> git remote --verbose
Git repository found, initializing review manager and pr tree view.
Thanks a lot!
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
The Predicted G-Protein-Coupled Receptor GPR-1 Is ... - NCBI
G-protein-coupled receptors (GPCRs) control important aspects of asexual and sexual development in eukaryotic organisms. We have identified a predicted GPCR ...
Read more >The Predicted G-Protein-Coupled Receptor GPR-1 Is ...
Localization studies using a GPR-1-greenfluorescent protein fusion protein showed that GPR-1 is targeted tofemale reproductive structures. Genetic epistasis ...
Read more >Module 1: What is Supply Chain Management? (ASU-WPC ...
Part 1 of 12 - This module introduces viewers to the field of supply chain management. It describes the complex supply chain of...
Read more >WT/DS54/R - World Trade Organization
If the Panel Report is appealed to the Appellate Body, it shall not be ... supports the view that Article III does not...
Read more >The biggest challenges, issues of supply chain management
6 River Systems explores the biggest supply chain issues and challenges. Find expert advice on how to overcome the challenges of supply ......
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

@AamuLumi I didn’t look closely at the VSCode version you had in the original post. I think the problem is from that. In our builds, we have a different
product.jsonthat whitelists some extensions as being able to use the proposed API so that we can self-host on the API. The OSS version doesn’t have this. Where are you getting your build from? If you’re building it yourself, you can addotherwise, if you launch with the flag
--enable-proposed-api GitHub.vscode-pull-request-githubit should workSame problem here,
Extension version: 0.1.6 VS Code version: 1.27.2 OS version: Linux x64
and same result when adding a remote.
I tried manually adding a Github Token, but the problem persists.