Automate Sesheta's acceptance of contributor invites [meteor]

AICoE / aicoe-ci

AICoE-CI using TektonCD pipelines and triggers

13 stars 13 forks source link

Automate Sesheta's acceptance of contributor invites [meteor] #126

Closed MichaelClifford closed 2 years ago

MichaelClifford commented 3 years ago

Is your feature request related to a problem? Please describe. I'm always frustrated when I have to wait an unknown amount of time for a human to accept my contributor invite to Sesheta and start using the AICoE-CI.

Describe the solution you'd like Sesheta automatically accepts contributor invites.

Describe alternatives you've considered None

Additional context This is relevant to making the user experience of the elyra tutorial with meteor smoother.

harshad16 commented 3 years ago

we will work on it . The procedure we would follow is:

user would need to open an issue follow this template: https://github.com/AICoE/aicoe-ci/issues/new?assignees=goern%2Charshad16&labels=area%2Fcyborgs%2Cbot%2Csig%2Fcyborgs&template=request_sesheta.yaml&title=Help+with+Sesheta+invite
then add automation to resolve them with bots. wdyt ?

goern commented 3 years ago

/cc @erikerlandson

goern commented 3 years ago

/kind feature /priority important-soon

sesheta commented 2 years ago

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.

/lifecycle stale

codificat commented 2 years ago

/remove-lifecycle stale /sig user-experience /triage accepted

sesheta commented 2 years ago

@codificat: The label(s) triage/accepted cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/AICoE/aicoe-ci/issues/126#issuecomment-968701910): >/remove-lifecycle stale >/sig user-experience >/triage accepted Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

sesheta commented 2 years ago

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.

/lifecycle stale

harshad16 commented 2 years ago

/remove-lifecycle stale

sesheta commented 2 years ago

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.

/lifecycle stale

sesheta commented 2 years ago

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.

/lifecycle rotten

sesheta commented 2 years ago

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

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/aicoe-ci/issues/126#issuecomment-1186731676): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.