Open mrbobbytables opened 5 years ago
As a note if it does come up:
https://kubernetes-contributor.netlify.com/calendar/
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
/remove-lifecycle stale
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
/remove-lifecycle stale
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
/lifecycle frozen
@mrbobbytables I suggest importing the key and events email-id from .env file
. What are your views, Sooner or later we will need an environment configuration file?
/joke
@aadarsh-nagrath: A termite walks into a bar and asks “Is the bar tender here?”
It's access is restricted to referrers from: https://kubernetes-contributor.netlify.com/calendar/
Is that URL still right?
AIs
/assign