Ability to specify push options
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 293
- PR merge metrics
- No merged PRs in 30d
Description
I need to pass some push options when pushing my changes - and I'm unable to see how/where to do this. Am after the equivalent of git push -o bob=foo.
Looks like libgit2 has the ability to init push_options, but I can't see how to pass this in rugged.
Any clues?
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 reading the Rugged push API and the libgit2 push_options documentation referenced in the issue. Identify the existing push-related tests or entry points, then determine how push options should be exposed and verify that an option such as git push -o bob=foo reaches libgit2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, git, ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100