Add support for delving into commit history
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Once all builds have been exhausted, there should be some mechanism for transgression to begin performing a git bisect on commit histories between two builds. This requires that we have the commits from which builds were made, as well as the ability to compile code (a build command).
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 locating the flow that runs after all builds have been exhausted, then trace how builds are associated with commits and how code is compiled. Define the entry point for bisecting between two builds and verify that it can use the required commits and build command to narrow the regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100