diff options
author | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2020-03-26 18:01:36 -0400 |
---|---|---|
committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2020-03-26 18:01:36 -0400 |
commit | 6de8a6106413068662ca2fa5a98ba2b6aa7f2d7b (patch) | |
tree | d6ac7295c40c740f09db0e9cc73e0052c11ad0e7 /thanks-pr-template.example | |
parent | 44ac4f1a78330f029343f31c46e46abc69a25121 (diff) | |
download | b4-6de8a6106413068662ca2fa5a98ba2b6aa7f2d7b.tar.gz |
Add initial "b4 pr" command set
While working on "pull-request exploder" stuff for achiving on
lore.kernel.org, I realized that this may be a useful set of features
for developers as well, so here is a very simple framework for handing
pull requests. Examples:
b4 pr <msgid>
- downloads that message
- parses the pull request
- checks that the remote tip is where the message says it should be
- makes sure the base-commit is present in the tree
- makes sure the tip commit isn't already in one of the branches
- checks if FETCH_HEAD already is at that commit
- if the above two checks pass, performs a git fetch
b4 pr --check <msgid>
Runs all of the checks above, but doesn't perform the actual fetch.
Useful if you don't remember if you've already processed a pull
request or not.
b4 pr --explode <msgid>
Runs basic sanity checks and then:
- performs a git fetch
- runs a "git format-patch" for base-commit..FETCH_HEAD
- adds the same to/from/cc headers as in the pull request
- properly threads each patch below the pull request
- saves that into a <msgid>.mbox file
The above is handy if you want to comment on something in a pull
request and not have to hunt around for sender/cc information.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Diffstat (limited to 'thanks-pr-template.example')
0 files changed, 0 insertions, 0 deletions