Problem with git log -2
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.2k
- Forks
- 851
- PR merge metrics
- No merged PRs in 30d
Description
When I test with git log -2, it wasn't able to explain -2
I am not sure if this is a supported operation of explainshell, or could something be done in this case?
Excellent tool and website. Keep up the good work! 😉
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
Reproduce the reported case with git log -2 using the explainshell URL and compare how -2 is handled against the rest of the command. The issue does not mention a file or test; done means explainshell either documents this argument or clearly reports why it cannot explain it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100