Keith Smiley
Keith Smiley
Right now the few configuration variables are all env vars, it might make sense to move this configuration to the gitconfig instead so it's in a standard place users likely...
If you submit a PR for a repo, then remove the main clone of that repo, reclone it, and submit another PR from it, the original worktree setup in the...
If you submit a pr with `git submitpr --onto SOMETHING` and then `git rebasepr` the chained PR, it is still rebased against the main branch.
``` % g submitpr --draft + command -v gh + commit_arg=HEAD + [[ 1 -gt 0 ]] + [[ --draft != --* ]] + [[ --draft == \-\-\o\n\t\o ]] ++...
If you resolve a conflict and manually edit and add another file in the rebase, when you rebasepr it won't pick up the manually edited change, using [replacepr](https://github.com/keith/git-pile/pull/39) can fix...
One thing I've found myself needing to do sometimes is take a PR, and "convert" it to a commit on my pile. I think I could create a `git pullpr`...
Right now you always have to specify a sha, this is a bit annoying if you have to `git log --oneline` or something first. I use a fuzzy finder to...
Right now you can run `git submitpr --onto foo` to submit a single PR against an specific sha, theoretically we could support something like `git submitpr sha1...sha2` that submitted multiple...
If you have a stack of PRs right now, you have to manually run rebasepr on each one as the bottom of the stack merges. Ideally you could do `git...