Support `git push --delete`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
The issue names no files. Start by finding where the existing push command is handled in the git2cpp command-line code and how it calls into libgit2, then see how a branch deletion would be expressed as a push refspec. Done means git push --delete <branch> removes the branch from the remote, which you can check by creating and pushing a branch in the git2cpp-test-private repo, deleting it, and confirming the remote no longer lists it.
Written by the indexing model from the issue text.
Description
Supporting git push --delete would be useful, to delete a remote branch. This could be tested using the git2cpp-test-private repo by creating and pushing a new branch, then deleting it and checking that the remote no longer has it.
- Dominant language
- C++
- Stars
- 7
- Forks
- 5
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 10
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from QuantStack/git2cpp
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
QuantStack/git2cpp#203 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuantStack/git2cpp#198 ·
Maintainers usually reply within 1 day
-
Checkout message duplicatedPossibly taken @ianthomas23 claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 25/100
QuantStack/git2cpp#202 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
QuantStack/git2cpp#131 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
QuantStack/git2cpp#62 ·
Maintainers usually reply within 1 day
All issues in QuantStack/git2cpp
Similar issues
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
BaptisteHudyma/Lamp-Da#588 ·
Maintainers usually reply within 1 day
-
bug macOS networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
docling-project/docling-parse#448 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
TokisanGames/Terrain3D#1073 ·
Maintainers usually reply within 1 day