From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Should the bot add PRs directly to TRACKER tickets?
Date: Sun, 27 Oct 2019 02:28:20 +1300 [thread overview]
Message-ID: <20191027022820.13afce1d@katipo2.lan> (raw)
In-Reply-To: <e25a4b90-3747-6938-6797-158e5a1a0da6@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
On Sat, 26 Oct 2019 14:24:22 +0200
Jonas Stein <jstein@gentoo.org> wrote:
> Here is an example:
> https://bugs.gentoo.org/683184
> In this case it is still quite tidy, but other TRACKERS will become
> unreadable by that.
I think in that case the PR bot should tell people:
- Find / Open the relevant bug
- Link to that instead
- Perform the dance required for the PR bot to recheck things.
And otherwise reject citing a tracker as a close/bug source in a PR.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-26 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 12:24 [gentoo-dev] RFC: Should the bot add PRs directly to TRACKER tickets? Jonas Stein
2019-10-26 13:28 ` Kent Fredric [this message]
2019-10-26 19:29 ` Thomas Deutschmann
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=20191027022820.13afce1d@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox