core/web/src/lib/components/repo/pipelines/ at sv-fe · alice.pds.demo.boltless.dev/core · Tangled

alice.pds.demo.boltless.dev / core

0

This repository has no description

0

core / web / src / lib / components / repo / pipelines

14 files

at sv-fe

eti web/components/pipelines: improve PipelineToolbar look 8d ago

PipelineCard.stories.svelte

web/components/pipelines: improve PipelineToolbar look Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineCard.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineCardContent.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineEmptyState.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineList.stories.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineList.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineSearch.stories.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineSearch.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineStatusIcon.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineToolbar.stories.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineToolbar.svelte

web/components/pipelines: improve PipelineToolbar look Signed-off-by: eti <eti@eti.tf>

1 week ago

PipelineWorkflows.svelte

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago

web: add repository pipelines page with mocked data Adds the pipelines tab at /[handle]/[repo]/pipelines. The cards follow the issue cards: what set the run off on top, then a status tag, a dropdown listing the workflows, when it ran and how long it took. While a run is still going the dropdown counts the finished ones, so 1/3. The data is fake for now. It sits in components/repo/pipelines/mock.ts and the page load filters it, so pointing this at bobbin later should only mean rewriting +page.ts. The search box and the push/pull-request tabs keep each other's state, so searching inside a tab does not throw the tab away. Along for the ride: Tag gained a danger colour for failed runs, DropdownItem takes a class and now renders Button, and Button exposes a bindable ref. The links to workflow logs point at a route that does not exist yet. Signed-off-by: eti <eti@eti.tf>

1 week ago