vscode-pull-request-github
vscode-pull-request-github copied to clipboard
microsoft
Can't create issues - "Creating issue failed: Issues are disabled for this repo" although enabled
- Extension version: GHPRI Nightly, v2021.3.42303
- VSCode Version: Codespaces Version: 1.55.0-insider Commit: c185983a683d14c396952dd432459097bc7f757f Date: 2021-03-30T12:43:45.267Z Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.82 Safari/537.36
- OS: Windows 10, Chrome browser
Steps to Reproduce:
-
Create a Codespace on https://github.com/bamurtaugh/communication-services-web-calling-hero
-
Attempt to create an issue
-
Fails with "Creating issue failed: Issues are disabled for this repo"
-
Check my repo, issues are enabled. However, I noticed they're disabled for the upstream from which I forked https://github.com/burkeholland/communication-services-web-calling-hero (although issues are enabled for the upstream from which Burke forked, https://github.com/Azure-Samples/communication-services-web-calling-hero)
Here are my remotes when using git remote -v:
I ran into this as the "owner" of the fork, and a collaborator I added to the fork also experienced this same behavior.
I saw https://github.com/microsoft/vscode-pull-request-github/issues/1517, which seems to be related here.
We try to be smart and when a repo is a fork, we figure that you are most likely to want to create an issue on the upstream.
Looks like we should fallback to the fork for creating the issue if we encounter this error.
@alexr00 What if we want to edit issues onto the fork/origin repo? Can we configure that somewhere? My Fork is the continuation of a disbanded project.
I have a similar issue, but slightly different symptom. Issues are enabled on the origin repo, I forked that repo and enabled issues on my own fork. If I add an issue to my fork via GitHub it does not appear in VSCode. If I add an issue via VSCode it logs under the origin, not my fork.
