Community: Bot should respond with the final step when a PR is accepted

Created on 29 Jan 2018 · 10Comments · Source: kubernetes/community

A new contributor gave me some bot feedback. All the intermediate steps were fine (bot had links to docs, etc.) but one thing he wasn't clear on was what the next step when his PR got accepted.

Perhaps something like "Your PR has been accepted, you're done! No action is required on your part. Check the _merge queue_ if you're interested in more details"

/sig contributor-experience

lifecyclrotten sicontributor-experience

Source

castrojo

👍3

Most helpful comment

@spxtr @cjwagner @fejta @spiffxp
Some feedback that might be helpful to keep in mind for tide (and it's status context).

cblecker on 1 Feb 2018

👍2

All 10 comments

@spxtr @cjwagner @fejta @spiffxp
Some feedback that might be helpful to keep in mind for tide (and it's status context).

cblecker on 1 Feb 2018

👍2

/help

castrojo on 7 Feb 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 8 May 2018

/remove-lifecycle stale
/remove-help

I don't think this is help wanted yet, because we don't have feedback on approach.

Do you still think this is a good idea, @castrojo? If so, I can put it in the backlog to discuss (trying to collect our issues together)

cblecker on 8 May 2018

Has there been any discussion on this?

Will this lead to too much spam? Maybe if we could figure out that the PR is sent by a new contributor (https://github.com/kubernetes/test-infra/issues/3083), we can put this info in the onboarding information?

nikhita on 13 Jun 2018

👍1

I think the intent here is to make the details for the tide context display this info for a given PR

fejta on 13 Jun 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 11 Sep 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 11 Oct 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 10 Nov 2018

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.