Any way to persist Github username and password to avoid prompt for git fork?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
I don't want to enter it for every repository I want to fork.
This seems to be the only command that contacts Github.com[1].
Would or could this read a .gitconfig file? I might actually like this separate, as I have both a private and public use for git tools on the same computer.
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 with the git fork command described in Commands.md and review how it currently contacts GitHub and prompts for credentials. Clarify whether credential persistence should use .gitconfig and how separate private and public identities should work; done should mean repeated forks no longer prompt while supporting those separate uses securely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100