run-llama/vibe-llama
1
0
Fork 0
mirror of https://github.com/run-llama/vibe-llama.git synced 2026-07-01 21:54:01 -04:00
Code Issues Packages Projects Releases 10 Wiki Activity

[PR #21] [MERGED] Copy paste in llamadeploy docs #23

New Issue
Closed
opened 2026-02-16 03:19:25 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 03:19:25 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

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

Base: main ← Head: adrian/llamadeploy

📝 Commits (2)

📊 Changes

5 files changed (+953 additions, -9 deletions)

View changed files

➕ documentation/llamadeploy.md (+939 -0)
📝 pyproject.toml (+1 -1)
📝 src/vibe_llama/sdk/base.py (+4 -6)
📝 src/vibe_llama/starter/data.py (+8 -1)
📝 uv.lock (+1 -1)

📄 Description

Copy pastes in llama deploy docs. I'm not looking forward to maintaining parity for these docs. (Probably will be a fair amount of changes)

Wondering how we should manage this going forward. Might be nice to somehow generate something like these docs in the site build, and have some configuration as to whether it uses "llms.txt" mode (llama index docs) or full docs. Not sure how to manage the custom chunking. The llama deploy docs here are just chunked by page 🤷

🔄 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/21 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 9/26/2025 **Status:** ✅ Merged **Merged:** 9/26/2025 **Merged by:** [@AstraBert](https://github.com/AstraBert) **Base:** `main` ← **Head:** `adrian/llamadeploy` --- ### 📝 Commits (2) - [`3e8995b`](https://github.com/run-llama/vibe-llama/commit/3e8995be7712474b8b55c8d60e611a7cb9fc4d48) Copy paste in llamadeploy docs :cry: - [`3cf0936`](https://github.com/run-llama/vibe-llama/commit/3cf093670e5f7e27f4d225210d1e167f28edae65) version bump ### 📊 Changes **5 files changed** (+953 additions, -9 deletions) <details> <summary>View changed files</summary> ➕ `documentation/llamadeploy.md` (+939 -0) 📝 `pyproject.toml` (+1 -1) 📝 `src/vibe_llama/sdk/base.py` (+4 -6) 📝 `src/vibe_llama/starter/data.py` (+8 -1) 📝 `uv.lock` (+1 -1) </details> ### 📄 Description Copy pastes in llama deploy docs. I'm not looking forward to maintaining parity for these docs. (Probably will be a fair amount of changes) Wondering how we should manage this going forward. Might be nice to somehow generate something like these docs in the site build, and have some configuration as to whether it uses "llms.txt" mode (llama index docs) or full docs. Not sure how to manage the custom chunking. The llama deploy docs here are just chunked by page 🤷 --- <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:25 -05:00
yindo closed this issue 2026-02-16 03:19:25 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
 wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/vibe-llama#23
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?