Disallowing at mentions and keywords which close issues in commit messages across all Kubernetes GitHub orgs

[Nikhita]

Hey all,

When a commit message containing at mentions (example: @nikhita) or keywords which close issues (example: fixes #XXX) is pulled into a fork, GitHub might take action on these keywords by:

- Pinging the person who is at mentioned, leading to excessive emails.

- If the person has write access to a repo, it will close issues that may not be ready to be closed.

Note that the keywords have these problems only if they are mentioned in the commit message - mentioning them in the PR body is fine.

To avoid these scenarios, we intend to enable the "invalidcommitmsg" prow plugin across all active Kubernetes GitHub orgs in this PR: https://github.com/kubernetes/test-infra/pull/12236.

If a PR has commits with messages containing these keywords, this plugin will automatically add the `do-not-merge/invalid-commit-message` label and add a comment specifically mentioning invalid commits so that they can be fixed.

Lazy consensus timeboxed to Friday, April 19, 5pm PT. Please chime in on the PR if you have any questions, concerns or objections.

Thanks,

Nikhita

[Davanum Srinivas]

+1 yes please!

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/CAFPyxn%2BNj_zvo2XoZvkMbHhMg9-R_kOzcGr2Mwnn3ks3UXsmvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Davanum Srinivas :: https://twitter.com/dims

[codyc]

Im 100% about this. +1

[Brian Grant]

Thank you!

You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CANw6fcH2Qu-Ttfs4WzK8OirkudJsoyCBo4X76JoZwDCgSYQANg%40mail.gmail.com.

[Josh Berkus]

On 4/16/19 7:00 PM, Nikhita wrote:
> Note that the keywords have these problems only if they are mentioned in
> the commit message - mentioning them in the PR body is fine.
>

I thought that having "Fixes #9999" in the PR body would *also* cause
the issue to close automagically. No?

--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS

[Jordan Liggitt]

It does, and that is desired. It is the spooky action at a distance as commits get pulled into unrelated forks/repos that is not desired.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-dev.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/cbae29ad-be8c-72b0-c70d-7c975b633623%40redhat.com.

[Josh Berkus]

On 4/17/19 9:26 AM, Jordan Liggitt wrote:
> It does, and that is desired. It is the spooky action at a distance as
> commits get pulled into unrelated forks/repos that is not desired.

Speaking as a member of the Release Team, we'd like to *also* disable
auto-close for some PRs in the body, but that sounds like it's a
different feature.

For example, we don't want e2e/conformance test fix PRs to auto-close
anything; those issues shouldn't close until the test is confirmed passing.

[Josh Berkus]

On 4/17/19 9:30 AM, Josh Berkus wrote:
> On 4/17/19 9:26 AM, Jordan Liggitt wrote:
>> It does, and that is desired. It is the spooky action at a distance as
>> commits get pulled into unrelated forks/repos that is not desired.
>
> Speaking as a member of the Release Team, we'd like to *also* disable
> auto-close for some PRs in the body, but that sounds like it's a
> different feature.
>
> For example, we don't want e2e/conformance test fix PRs to auto-close
> anything; those issues shouldn't close until the test is confirmed passing.
>

Oh, and to be clear: +1 on the commit message change.

[Erick Fejta]

+1 this is a fantastic change. These types of messages cause confusion and annoyance (especially as people push the commits into their forks). Will be great to help people not make them.

> we'd like to *also* disable auto-close for some PRs in the body

FYI I know that many of us already know this, but all of this action is done by github. It is not behavior we coded into our bots.

This is unfortunate because when k8s-ci-robot pushes a commit with a "fixes #123" comment github "helpfully" closes #123 and adds a message on #123 saying that k8s-ci-robot closed the issue, which is mostly untrue and not something it has a choice over. But it causes confusion and we get the occasional support question about it.

This is different from what happens when someone leaves a comment to an issue with a "/close" line. In this scenario it triggers code that we wrote and control that causes the bot to validate the request and call the github's close api on that issue. We can change this behavior as we need. Unfortunately, we cannot control what github does with a fixes #123 comment/commit.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/c8d1e350-0dd5-aaff-59f6-5afa37f83055%40redhat.com.

[Josh Berkus]

On 4/17/19 9:59 AM, Erick Fejta wrote:
> +1 this is a fantastic change. These types of messages cause confusion
> and annoyance (especially as people push the commits into their forks).
> Will be great to help people not make them.
>
>
>> we'd like to *also* disable auto-close for some PRs in the body
>
> FYI I know that many of us already know this, but all of this action is
> done by github. It is not behavior we coded into our bots.

I want to move this discussion to an issue, so that we don't drag out
the approval of nikhita's very helpful patch.

https://github.com/kubernetes/test-infra/issues/12240

[Aaron Crickenberger]

Explicit +1 for enabling the invalid commit message plugin across all kubernetes orgs

- aaron

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/e4513d14-4fb1-7edb-dbe7-af04c88c12cc%40redhat.com.

[Benjamin Elder]

+1, please do!

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/CALOex7ub5ZueVSo9rtW5Vw0vcfgQnNn0DUFjAfVLVYWCmBOnGA%40mail.gmail.com.

[Christoph Blecker]

This is now merged and active. Thanks everyone!

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/CAOZRXm-u9Va7nyUV6jHezQtZ_zLMB5LuHxLHoaw%2BfooaqVK_4g%40mail.gmail.com.

[Di Xu]

+1000! Awesome.