git-pull-request (and others) support for acccess tokens
Open
Nobody has claimed this yet.
enhancement
pull request is welcome
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
For repos that use SAML SSO, email, password, and 2fa otp aren't sufficient., and GitHub kicks back that you must configure a Personal Access Token. It doesn't look like the git-pull-request script is able to support that. Perhaps it could read from an env var GITHUB_TOKEN or something similar? Then we could keep those secure in e.g. a .env file.
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 locating the git-pull-request script and the other scripts referred to in the issue, then inspect how they authenticate with GitHub. Done means a Personal Access Token supplied through an environment variable can support repositories using SAML SSO while keeping the token out of command arguments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- authentication, cli, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100