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
{{ message }}
This repository was archived by the owner on Feb 8, 2024. It is now read-only.
This may just be that I don't really understand the updated_at field within a pipeline, but when I restart a workflow within a pipeline, the updated_at value doesn't change... It would be nice if this changed if any one of its descendants (workflow or job within the pipeline) changed status themselves. It would also be nice if the .../pipeline endpoint returned a list of pipelines sorted based on a query parameter. For instance, I'd sort based on updated_at vs. created_at. Any suggestions?
Hi,
This may just be that I don't really understand the updated_at field within a pipeline, but when I restart a workflow within a pipeline, the updated_at value doesn't change... It would be nice if this changed if any one of its descendants (workflow or job within the pipeline) changed status themselves. It would also be nice if the .../pipeline endpoint returned a list of pipelines sorted based on a query parameter. For instance, I'd sort based on updated_at vs. created_at. Any suggestions?
Schuyler