Create a sequence diagram of CI that is doing a provenance check

thoth-station / core

Using Artificial Intelligence to analyse and recommend Software Stacks for Artificial Intelligence applications.

https://thoth-station.github.io/

GNU General Public License v3.0

28 stars 25 forks source link

Create a sequence diagram of CI that is doing a provenance check #253

Open pacospace opened 4 years ago

pacospace commented 4 years ago

Is your feature request related to a problem? Please describe. In order to show how a user can benefit from Thoth, it would be nice to see how provenance check can be used in CI pipeline

Describe the solution you'd like Create a sequence diagram.

Describe alternatives you've considered

Additional context

sesheta commented 3 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

goern commented 3 years ago

/remove-lifecycle stale /sig docs

sesheta commented 3 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 3 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/thoth-station/core/issues/253#issuecomment-880591196): >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.

goern commented 3 years ago

/triage accepted /assign @goern

goern commented 3 years ago

/unassign goern /assign pacospace

Please take over the conversation with @dneary

sesheta commented 3 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 3 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 3 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/thoth-station/core/issues/253#issuecomment-905047292): >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.

sesheta commented 3 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 3 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 3 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/thoth-station/core/issues/253#issuecomment-926446838): >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.

dneary commented 3 years ago

I am unclear if there is any conversation to be had - @pacospace is this something we should spend time on?

codificat commented 3 years ago

Rotten issues close after 30d of inactivity.

There was a bug in prow at the time of that comment: it was not rotten back then (and certainoy not for 30 days). That bug is now fixed.

Reopen the issue with /reopen.

/reopen /lifecycle frozen

sesheta commented 3 years ago

@codificat: Reopened this issue.

In response to [this](https://github.com/thoth-station/core/issues/253#issuecomment-966217288): >> Rotten issues close after 30d of inactivity. > >There was a bug in prow at the time of that comment: it was not rotten back then (and certainoy not for 30 days). That bug is now fixed. > >> Reopen the issue with `/reopen`. > >/reopen >/lifecycle frozen 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.

codificat commented 3 years ago

/remove-lifecycle rotten /lifecycle frozen