Question about using git pr
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
When reviewing PR's, I use git pr a lot, and I am very grateful to have it.
Now that GitHub allows pushing to changes back to the original source branch for a PR (assuming the submitter has allowed this) what would be required, or should be used in conjunction with git pr, to allow the easy checkout of the PR branch, but also allow local changes and pushing back?
Thanks in advance!
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 pr command and the checkout and push workflow described in the issue. Determine how a PR branch can be checked out while preserving a remote suitable for pushing changes back, then verify the behavior against GitHub's permitted contributor push flow. Done means the workflow is clearly supported or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100