microsoft / microsoft/vscode-bisect
Bisect should include the bad commit
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 10
- Avg merge
- 55m
- Merged PRs (30d)
- 1
Description
- Bisect with
c6b48c364dde70c12bf977f1da50acda0fd801e3as bad and8762127fc97b8aaae5f3a0dd6a6d853d9a1b7574as good - Note it says 3 builds in 2 steps
- Try to repro the bug that is when you alt tab your folders get collapsed
- Note all builds in the steps are good
- The bisect tool tells me "all builds are good"
This was a bit confusing to me and I wish it would state that the bad build is the only bad one so I know what commits to narrow down on
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 by reproducing the listed bisect scenario with c6b48c364dde70c12bf977f1da50acda0fd801e3 as bad and 8762127fc97b8aaae5f3a0dd6a6d853d9a1b7574 as good, then inspect how the bisect tool reports "all builds are good." Done means the output clearly explains that the bad build is the only bad one and helps identify which commits to narrow down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100