`peel` arguments inconsistent.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
Description
peel is implemented twice, once in object.c and once in reference.c. In the first it requires an argument and in the second it provides a default argument of None. This is confusing when branches can be 'default' peeled but tags cannot.
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
Compare the two peel implementations in object.c and reference.c, focusing on their argument handling for branches and tags. Establish one consistent behavior for the optional argument, then verify that both implementations expose the same interface and that default peeling remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100