microsoft / microsoft/vscode-pull-request-github
Closed PRs get associated with new branches of the same name
Offen
@alexr00 arbeitet bereits daran.
Seit 07.5.2025.
bug
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2.6k
- Forks
- 796
- Ø Merge
- 1 T. 4 Std.
- Gemergte PRs (30 T.)
- 46
Beschreibung
Sometimes, when I create a branch, I will find it becomes associated with a wrong PR that was previously closed and used the same branch name.
This can mean if you run the "delete local branches and remotes" command it will wrongly delete your branch.
- Extension version: 0.106.0
- VSCode Version: 1.98.0 (system setup)
- OS: Windows_NT x64 10.0.22631
- Repository Clone Configuration: fork of an upstream repository
- Github Product: Github.com
Steps to Reproduce:
Unknown. Note in .git/config you might see something like:
[branch "dev"] # this branch was created a few days ago
remote = origin
merge = refs/heads/dev
vscode-merge-base = origin/dev
github-pr-owner-number = "cylc#cylc-ui#810"
github-pr-owner-number = "cylc#cylc-ui#810"
github-pr-owner-number = "cylc#cylc-ui#810"
github-pr-owner-number = "cylc#cylc-ui#810"
github-pr-owner-number = "cylc#cylc-ui#810" # this is a PR that was closed 4 years ago!
or
[branch "log-wrap"]
vscode-merge-base = origin/master
remote = origin
github-pr-owner-number = "cylc#cylc-ui#1708"
github-pr-owner-number = "cylc#cylc-ui#1708"
github-pr-owner-number = "cylc#cylc-ui#1708"
github-pr-owner-number = "cylc#cylc-ui#1708"
github-pr-owner-number = "cylc#cylc-ui#2078" # finally the correct one!
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.