Since PRs are a second class citizen to Jira, mostly used for a scratch pad for nits and questions with code context, I suspect any improvements here will need to be automated to have any hope of success.
From: Stefan Miklosovic <stefan.mikloso...@instaclustr.com> Date: Wednesday, 16 March 2022 at 08:16 To: dev@cassandra.apache.org <dev@cassandra.apache.org> Subject: Re: Using labels on pull requests in GitHub Yeah, what I see quite frequently is that people come over, they open PR but it does not have any related JIRA ticket and they just drop it there and never return hence these PRs are in a constant limbo, not in JIRA and they are more often than not left behind completely. Creating categories would at least provide some minimal visibility where we are at. On Wed, 16 Mar 2022 at 09:07, Erick Ramirez <erickramire...@apache.org> wrote: > > +1 it's a great idea. I have to admit that I don't go through the PRs and I > only pay attention to tickets so if doc PRs are "orphans" (don't have > associated tickets), I don't ever work on them. I'll aim to do this when I > have bandwidth. Cheers! 🍻 > > On Wed, 16 Mar 2022 at 19:02, Stefan Miklosovic > <stefan.mikloso...@instaclustr.com> wrote: >> >> Hello, >> >> Is somebody fundamentally opposing the idea of applying labels to pull >> requests when applicable? I went through the pull requests and it >> would be nice to have some basic filters, like "show me all pull >> requests related to documentation" would be labeled as "docs", then >> PRs fixing some tests would be "tests" and so on. We may further >> narrow it down for subsystems etc. >> >> I do not mind applying myself in this to tag the PRs as they come if >> people do not tag it themselves in order to have at least some basic >> "filterability". As I went through PRs closing already committed ones, >> I noticed there are a lot of PRs related to documentation which just >> tend to be completely forgotten in the long run. >> >> Does this make sense to people? >> >> Regards >> >> Stefan
