Order of commits
Open
Nobody has claimed this yet.
benchable
committable
testneeded
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<MasterDuke> benchable6: bfbf348..c069f45 for ^1000_000 { }
<benchable6> MasterDuke, starting to benchmark the 29 given commits
<benchable6> MasterDuke, https://gist.github.com/ecc7a8d7a12dad58d6458ca238d89ed7
<AlexDaniel> MasterDuke: hey… if the fix is in 5401a1a, then why is it only visible in f94cb21 ?
<MasterDuke> 5401a1a is newer than f94cb21
<AlexDaniel> whoa?
<MasterDuke> for some reason that graph has the newer commits on the left
<AlexDaniel> whoa?? :O
<AlexDaniel> no… no… can't be
<AlexDaniel> yes, 5401a1a is indeed newer… f94cb21 is its parent
<AlexDaniel> but then wtf?
<MasterDuke> don't know why
Contributor guide
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
The issue names no file, test, or entry point. Start by reproducing the benchmark and commit graph shown in the transcript, using the linked gist, and compare the ordering of 5401a1a with its parent f94cb21. Done means the displayed commit order reflects the actual parentage and the behavior has a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100