-
Notifications
You must be signed in to change notification settings - Fork 720
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded
Milestone
Description
- Extension version: 0.92.0
- VSCode Version: 1.91.1 f1e16e1e6214d7c44d078b1f0607b2388f29d729 x64
- OS: Debian 12 (Bookworm)
- Repository Clone Configuration: Single repository
- Github Product: Github.com
Steps to Reproduce:
- Use the command GitHub Pull Requests: Create Pull Request
- Start writing
- Check something in another sidebar tab in the UI
- The tab "Github Pull Request" in de sidebar has disappeared, which is better than that it stays when I'm not making a PR.
- Re-issue the command GitHub Pull Requests: Create Pull Request to continue your PR
- UI loads, with all entered data visible
- UI resets all entered fields automatically
While it is understandable that this happens, it is extremely obnoxious. The UI taunts me with the data I just entered, and then quickly throws it away before I can do anything. Most PRs I make in VSCode I have to write twice or thrice. You'd think I'd learn.
Is it possible that step 7 is prevented when the tab is re-entered from GitHub Pull Requests: Create Pull Request if the source and target branches haven't changed?
Note: I don't want the sidebar tab Github Pull Request to be visible in the sidebar normally:
- It's visually indistinct (maybe even indistinguishable?) from the Github Pull Requests tab.
- There's hardly ever any use for it, except for when actively using it.
Note: It's easier to reproduce, but the steps above also show the workflow that causes me to run into this issue. The simplest reproduction:
- Use the command GitHub Pull Requests: Create Pull Request
- Start writing
- Use the command GitHub Pull Requests: Create Pull Request
- UI resets all entered fields automatically
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded