Skip to content

Make aicoe-ci independent from Sesheta #136

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
Open
pacospace opened this issue Sep 1, 2021 · 4 comments
Open

Make aicoe-ci independent from Sesheta #136

pacospace opened this issue Sep 1, 2021 · 4 comments
Assignees
@harshad16
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@pacospace
Copy link

pacospace commented Sep 1, 2021 •
edited
Loading

Is your feature request related to a problem? Please describe.
As AICOE Maintainer,

I want to facilitate the ingrations of Thoth and AICoE-CI services for users.
In this way users do not have to wait for sesheta invites approved.

Describe the solution you'd like
Make aicoe-ci independent from Sesheta.

Describe alternatives you've considered
Make users open issues and wait for invites approved.

Additional context
See: #135
See: #126
See: #138
See: #139
@pacospace pacospace added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/feature Categorizes issue or PR as related to a new feature. labels Sep 3, 2021
This was referenced Sep 3, 2021
Closed
Closed
@sesheta
Copy link
Contributor

sesheta commented Dec 2, 2021

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 sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2021
@codificat
Copy link
Member

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2021
@sesheta
Copy link
Contributor

sesheta commented Mar 2, 2022

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 sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2022
@harshad16
Copy link
Member

/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@harshad16 harshad16

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@codificat @harshad16 @pacospace @sesheta