[PR #15] [MERGED] workflows scaffolding #17

Closed
opened 2026-02-16 03:19:24 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/run-llama/vibe-llama/pull/15
Author: @adrianlyjak
Created: 9/4/2025
Status: Merged
Merged: 9/4/2025
Merged by: @AstraBert

Base: clelia/workflows-scaffoldingHead: adrian/workflows-scaffolding


📝 Commits (5)

📊 Changes

18 files changed (+433 additions, -181 deletions)

View changed files

hello/world/README.md (+56 -0)
hello/world/pyproject.toml (+10 -0)
hello/world/workflow.py (+147 -0)
📝 pyproject.toml (+5 -1)
📝 src/vibe_llama/main.py (+11 -7)
📝 src/vibe_llama/scaffold/__init__.py (+2 -3)
src/vibe_llama/scaffold/copy_templates.py (+0 -33)
src/vibe_llama/scaffold/project_files.py (+0 -74)
📝 src/vibe_llama/scaffold/scaffold.py (+36 -30)
📝 src/vibe_llama/scaffold/terminal.py (+3 -2)
templates/base_example/pyproject.toml (+10 -0)
templates/document_parsing/pyproject.toml (+10 -0)
templates/human_in_the_loop/pyproject.toml (+10 -0)
templates/invoice_extraction/pyproject.toml (+10 -0)
templates/rag/pyproject.toml (+11 -0)
templates/web_scraping/pyproject.toml (+10 -0)
📝 tests/scaffold/test_scaffold.py (+12 -27)
📝 uv.lock (+90 -4)

📄 Description

Selfishly, I would like these workflows to be fully functional templates that can easily be cloned with copier for easier integration into llamactl. I re-implemented functionality with copier here. We could also sneak some minor pyproject.toml configurations into them to point at their entry, and I think they can function then as headless llama-deploy workflows

The other issue you'll run into is that the templates currently aren't being bundled into the packaged vibe-llama. I added hatchling configuration to do so here.

image

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/vibe-llama/pull/15 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 9/4/2025 **Status:** ✅ Merged **Merged:** 9/4/2025 **Merged by:** [@AstraBert](https://github.com/AstraBert) **Base:** `clelia/workflows-scaffolding` ← **Head:** `adrian/workflows-scaffolding` --- ### 📝 Commits (5) - [`a862a39`](https://github.com/run-llama/vibe-llama/commit/a862a39b344ff46933a58dd9f2b41dd010ca7437) copier - [`ba463ff`](https://github.com/run-llama/vibe-llama/commit/ba463ff36da9a10e1905fde1ce36a8d93e1deb12) Fix tests, switch back to string - [`7b12148`](https://github.com/run-llama/vibe-llama/commit/7b12148b5fbb54428188cbe09ecc6d92c52d9c3c) oops - [`8ab6e10`](https://github.com/run-llama/vibe-llama/commit/8ab6e10d51345c6445c0f348778896a275c8a477) Fix lint - [`961bac3`](https://github.com/run-llama/vibe-llama/commit/961bac3b5d00a9c6a50762b0689bc833786c63ee) fix: path traversal now works with editable and non-editable installation ### 📊 Changes **18 files changed** (+433 additions, -181 deletions) <details> <summary>View changed files</summary> ➕ `hello/world/README.md` (+56 -0) ➕ `hello/world/pyproject.toml` (+10 -0) ➕ `hello/world/workflow.py` (+147 -0) 📝 `pyproject.toml` (+5 -1) 📝 `src/vibe_llama/main.py` (+11 -7) 📝 `src/vibe_llama/scaffold/__init__.py` (+2 -3) ➖ `src/vibe_llama/scaffold/copy_templates.py` (+0 -33) ➖ `src/vibe_llama/scaffold/project_files.py` (+0 -74) 📝 `src/vibe_llama/scaffold/scaffold.py` (+36 -30) 📝 `src/vibe_llama/scaffold/terminal.py` (+3 -2) ➕ `templates/base_example/pyproject.toml` (+10 -0) ➕ `templates/document_parsing/pyproject.toml` (+10 -0) ➕ `templates/human_in_the_loop/pyproject.toml` (+10 -0) ➕ `templates/invoice_extraction/pyproject.toml` (+10 -0) ➕ `templates/rag/pyproject.toml` (+11 -0) ➕ `templates/web_scraping/pyproject.toml` (+10 -0) 📝 `tests/scaffold/test_scaffold.py` (+12 -27) 📝 `uv.lock` (+90 -4) </details> ### 📄 Description Selfishly, I would like these workflows to be fully functional templates that can easily be cloned with copier for easier integration into llamactl. I re-implemented functionality with copier here. We could also sneak some minor pyproject.toml configurations into them to point at their entry, and I think they can function then as headless llama-deploy workflows The other issue you'll run into is that the templates currently aren't being bundled into the packaged vibe-llama. I added hatchling configuration to do so here. <img width="732" height="419" alt="image" src="https://github.com/user-attachments/assets/048537d1-19fd-4939-bec3-a1f922155b45" /> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 03:19:24 -05:00
yindo closed this issue 2026-02-16 03:19:24 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/vibe-llama#17