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 has been archived by the owner on Dec 7, 2023. It is now read-only.
Another quality-of-life improvement for pipeline-heavy workflows, is having "one-click pipelines" that (as the name implies) don't require any configuration, and run instantly when you click them.
This can again be made client-side only for now, but could be migrated to a server-side implementation once user sessions are a thing.
The idea would be as follows:
You can create a "one-click pipeline" based on an existing pipeline by opening that pipeline, filling in all required details, and instead of running the pipeline, selecting "save", and giving the pipeline a name.
These pipelines are visually distinct from others.
They also have their description removed, as it's assumed you know what it does, so that they take less room in the list of pipelines.
Another quality-of-life improvement for pipeline-heavy workflows, is having "one-click pipelines" that (as the name implies) don't require any configuration, and run instantly when you click them.
This can again be made client-side only for now, but could be migrated to a server-side implementation once user sessions are a thing.
The idea would be as follows:
As for the implementation itself, there are a few things to do:
name ➜ { pipelineId, variables }
.Not sure yet what the best way is to one-click pipelines, but I guess we could start by adding a small
x
to the left of the pipeline on hover.The text was updated successfully, but these errors were encountered: