`remote.pushDefault`
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.6k
- Forks
- 357
- Avg merge
- 15h 47m
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem? Please describe.
I use remote.pushDefault set to origin to always push to my own fork of projects. When I push via neogit there doesn't seem to be an option to push to the pushDefault without setting the pushRemote for the branch.
Describe the solution you'd like
If remote.pushDefault is set I would like Pd to push to it without setting the pushRemote for the branch.
Describe alternatives you've considered
Maybe I missed how to push to the pushDefault?
Just living with the fact that pushRemote is set for all my branches even though I don't need it.
Additional context
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
Start by tracing the Pd push command and compare its remote selection with Git's remote.pushDefault behavior described in the linked git-config documentation. Done means Pd uses the configured pushDefault when present without requiring a branch pushRemote, while preserving the existing behavior otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, lua, neovim
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100