From: Brian Masney <masneyb@kernel.org>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Brian Masney <masneyb@kernel.org>
Subject: [PATCH b4 0/3] review: add support for b4.pw-key-command
Date: Thu, 15 Oct 2026 10:08:40 -0400 [thread overview]
Message-ID: <20261015-pw-key-command-v1-0-6daa9b8cee2a@kernel.org> (raw)
Currently the patchwork token needs to be stored plaintext in your git
configuration. This series adds support for b4.pw-key-command so that
the token can be stored in a password manager.
Signed-off-by: Brian Masney <masneyb@kernel.org>
---
Brian Masney (3):
review: centralize lookup of patchwork key in one place
review: introduce support for b4.pw-key-command
review: tests: add tests for get_pw_key() and b4.pw-key-command
docs/config.rst | 16 ++++++++++++
src/b4/__init__.py | 53 ++++++++++++++++++++++++++++++++++++--
src/b4/review/_review.py | 4 +--
src/b4/review_tui/_common.py | 2 +-
src/b4/review_tui/_entry.py | 2 +-
src/b4/review_tui/_tracking_app.py | 2 +-
src/tests/test___init__.py | 53 ++++++++++++++++++++++++++++++++++++++
7 files changed, 125 insertions(+), 7 deletions(-)
---
base-commit: 6be7c6139d7734d84afddf989fa2874935b6d85b
change-id: 20261015-pw-key-command-12c3634b2e8f
Best regards,
--
Brian Masney <masneyb@kernel.org>
next reply other threads:[~2026-10-15 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:08 Brian Masney [this message]
2026-10-15 14:08 ` [PATCH b4 1/3] review: centralize lookup of patchwork key in one place Brian Masney
2026-10-15 14:08 ` [PATCH b4 2/3] review: introduce support for b4.pw-key-command Brian Masney
2026-10-15 14:08 ` [PATCH b4 3/3] review: tests: add tests for get_pw_key() and b4.pw-key-command Brian Masney
2026-10-19 17:28 ` [PATCH b4 0/3] review: add support for b4.pw-key-command Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261015-pw-key-command-v1-0-6daa9b8cee2a@kernel.org \
--to=masneyb@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.