search

AICoE / sefkhet-abwy

This is one of the incarnations of Sesheta
GNU General Public License v3.0
5 stars 13 forks source link

Create commands that will assist with creating Thoth releases #184

Closed fridex closed 2 years ago

fridex commented 2 years ago

Ex: create a new command for Sesheta “@sesheta schema updated” and sesheta will open “Kebechet update” issues to all the repositories that require thoth-storages Ex. create a new command for Sesheta “@sesheta component schema release“ and sesheta will open “New patch release” to all the components that have thoth-storages The list of components that use thoth-storages is static and can be maintained in sesheta Workflow: “@sesheta schema updated” ➡️ ☕ ➡️ “@sehsta component schema release” Later automate version bumps in thoth-application repository Avoid manual work https://github.com/thoth-station/thoth-application/issues/2091#issuecomment-963061022

Reference: https://docs.google.com/document/d/1XmXYEWEwgOBHqdJkUTmhBvUb41pr5GIR2pePasvvZ1s/edit#

fridex commented 2 years ago

/priority important-soon /triage accepted

sesheta commented 2 years ago

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

In response to [this](https://github.com/AICoE/sefkhet-abwy/issues/184#issuecomment-966444730): >/priority important-soon >/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

codificat 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/sefkhet-abwy/issues/184#issuecomment-1191274205): >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.