Bot for stale vendored cluster API about cluster-api HOT 9 CLOSED

Another thing this could do: automatically send PRs for out of date docker base images.

from cluster-api.

I've started on this ... a PR that is created by my WIP script kubernetes-sigs/cluster-api-provider-gcp#33

(I'm trying to figure out how this should behave in general - feedback welcome)

from cluster-api.

/assign

from cluster-api.

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

from cluster-api.

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

from cluster-api.

/remove-lifecycle rotten

from cluster-api.

I don't believe we need to automate updating a repo's vendoring of cluster-api. I suggest we close this issue. WDYT?

from cluster-api.

As suggested by @dhellmann, I'm going to close and we can always reopen issues if needed.

/close

from cluster-api.

@ncdc: Closing this issue.

from cluster-api.