Test-infra: A prow cmd to dup a github issue

Created on 4 Oct 2018 · 11Comments · Source: kubernetes/test-infra

similar to #9690 , we need a cmd to duplicate an issue, i.e. /dup

lifecyclrotten

Source

jessiezcc

Most helpful comment

so yeah, uh, welcome to the live demo of what those commands would do

spiffxp on 5 Oct 2018

😄7 🎉5

All 11 comments

Why? Do you mean you would like a command to copy a GitHub issue into another, identical, GitHub issue against the same repo?

stevekuznetsov on 4 Oct 2018

👍1

I meant to resolve an issue as a duplicated issue. It happens when there are 2(or more) separate issues tracking the similar problems/asks.

jessiezcc on 4 Oct 2018

A human can do this today via

/triage duplicate
because #1234
/close

What behavior would you be looking for in this case?

spiffxp on 5 Oct 2018

😄1

@spiffxp: Closing this issue.

In response to this:

A human can do this today via
/triage duplicate
because #1234
/close
What behavior would you be looking for in this case?

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.

k8s-ci-robot on 5 Oct 2018

/reopen
/remove-triage duplicate
THANKS PROW
TIL it'll interpret commands in ``` blocks

spiffxp on 5 Oct 2018

@spiffxp: Reopening this issue.

In response to this:

/reopen
/remove-triage duplicate
THANKS PROW
TIL it'll interpret commands in ``` blocks

k8s-ci-robot on 5 Oct 2018

so yeah, uh, welcome to the live demo of what those commands would do

spiffxp on 5 Oct 2018

😄7 🎉5

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 3 Jan 2019

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 2 Feb 2019

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 4 Mar 2019

@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