Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PR Dashboard: Incoming PR still included in the list after merge #4298

Closed
mbohlool opened this issue Aug 31, 2017 · 3 comments
Closed

PR Dashboard: Incoming PR still included in the list after merge #4298

mbohlool opened this issue Aug 31, 2017 · 3 comments
Assignees
@rmmh
Labels
area/gubernator Issues or PRs related to code in /gubernator kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@mbohlool
Copy link
Contributor

mbohlool commented Aug 31, 2017 •
edited
Loading

I assume the merged PRs should not be listed in this dashboard. I have at least some example of otherwise:

kubernetes/kubernetes#48151
kubernetes/kubernetes#47263

These show up in my dashboard:
@0xmichalis 0xmichalis mentioned this issue Sep 2, 2017
Closed
@0xmichalis 0xmichalis added the area/gubernator Issues or PRs related to code in /gubernator label Sep 2, 2017
@0xmichalis 0xmichalis mentioned this issue Nov 3, 2017
Closed
@0xmichalis 0xmichalis added the kind/bug Categorizes issue or PR as related to a bug. label Nov 3, 2017
@rmmh rmmh mentioned this issue Jan 10, 2018
Merged
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 7, 2018
@fejta-bot
Copy link

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
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 9, 2018
@rmmh
Copy link
Contributor

rmmh commented Mar 30, 2018

Fixed in #6230.

@rmmh rmmh closed this as completed Mar 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmmh rmmh

Labels
area/gubernator Issues or PRs related to code in /gubernator kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@rmmh @mbohlool @0xmichalis @k8s-ci-robot @fejta-bot