You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
Provide a way to configure how many runs for a given can be running at once. This feature has come up a few times across a bunch of issues in Pipelines (and was added to the roadmap):
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
dibyom
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
Apr 22, 2022
kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
Feature request
Provide a way to configure how many runs for a given can be running at once. This feature has come up a few times across a bunch of issues in Pipelines (and was added to the roadmap):
In addition, this was also proposed as a experimental project: #699
Use case
Next step: Gather requirements/use cases.
The text was updated successfully, but these errors were encountered: