microsoft / microsoft/vscode-pull-request-github
Selecting `Approved` from the dropdown should not auto submit
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 796
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 46
Description
Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/5300
Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/7028
I'd like to once again bring this issue up, because using a drop down to submit an action feels very unprecedented to me.
Like those other issues, I expect that hitting Approve here will change the blue Comment box from saying Comment to Approve, but will not submit the PR approval yet.
To me that feels like a 1:1 mapping of the behavior of switching to the Approve radio button. Just clicking that radio button does not auto submit the PR.
I often know I'm going to approve the PR, but haven't written my final approval comments in the box yet. On the github UI I'll change the radio button then go back and fill in the comments. I can't do this from the vs code extension and I end up double submitting so often 😢 .
I do like that if you widen the sidebar, then you see the 3 options inline in blue box form
If you are unwilling to make the drop down be a pure "switcher", then at the very least if you could please style this drop down the same as the Create Merge Commit drop down, I think that would resolve a lot of my confusion.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start at the pull-request review action dropdown and compare its behavior and styling with the Create Merge Commit dropdown; done means selecting Approve changes the review action without submitting it, allowing comments to be entered first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100