diff options
author | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2022-06-21 16:17:22 -0400 |
---|---|---|
committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2022-06-21 16:17:22 -0400 |
commit | b7d71d8de67bd238f65db6d142a22d7d5a79206d (patch) | |
tree | d125ec42dfe65d63cc066d5974b1ae008c8e5c18 /thanks-pr-template.example | |
parent | 409c865175bf8f103bf5633331e8a1d77a446814 (diff) | |
download | b4-b7d71d8de67bd238f65db6d142a22d7d5a79206d.tar.gz |
Initial patchwork integration support
A lot of maintainers use patchwork alongside b4, to make it easier to
track patches and rely on some CI integration. This commit adds some
basic patchwork integration:
- on "b4 am", "b4 shazam", "b4 pr" we will mark the relevant patchwork
entries as "Under Review"
- on "b4 ty" we can set these patches as "Accepted"
- on "b4 ty -d" we can set them as "Deferred"
To make it work, the following entries must be present in the repository
used with b4:
[b4]
pw-key = (your API token)
pw-url = https://patchwork.kernel.org
pw-project = (your project, e.g. linux-usb)
pw-review-state = under-review
pw-accept-state = accepted
pw-discard-state = deferred
To get your patchwork API token, go to your patchwork profile page.
The pw-accept-state and pw-discard-state can be overridden using the
--pw-set-state flag to "b4 ty". E.g. if you wanted to mark the patches
as "Not applicable":
b4 ty -d 5 --pw-set-state not-applicable
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Diffstat (limited to 'thanks-pr-template.example')
0 files changed, 0 insertions, 0 deletions