microsoft / microsoft/vscode-pull-request-github
On Issue, "checkout topic branch" should use existing branch if already created in UI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 795
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 46
Description
This is similar to #4120, but not identical.
There is a feature in the UI of the website, in the right side-bar of an issue, under "Development", to create a branch for an issue.
In VS Code PR and Issue view, under "Issues > Recent Issues", when clicking on an issue then the arrow to "Start working on issue and checkout topic branch", my feature requirements are :
- if a branch has already been created for this issue, use this branch instead of creating a new one
- if creating a new branch from here, give the user to rename this branch, and attach it to the issue so that it is visible in the issue side-bar on the github website, under the "Development" section
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
Start in the VS Code PR and Issue view's Issues > Recent Issues flow and trace the command behind “Start working on issue and checkout topic branch.” Check how the GitHub issue's Development branch association is represented. Done means an existing issue branch is reused, while a newly created branch can be renamed and attached to the issue for display in GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100