run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-07-21 04:05:25 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[PR #321] [MERGED] Clarify Agent Builder deployment workflow and iteration safety #324

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/321
Author: @adrianlyjak
Created: 2/3/2026
Status: ✅ Merged
Merged: 2/3/2026
Merged by: @adrianlyjak

Base: main ← Head: claude/slack-docs-agent-builder-deployment-wsBVW

📝 Commits (1)

  • 79f1fff docs: clarify that Agent Builder changes require explicit redeployment

📊 Changes

1 file changed (+13 additions, -4 deletions)

View changed files

📝 docs/src/content/docs/llamaagents/cloud/builder.md (+13 -4)

📄 Description

Summary

Updated documentation to clarify the relationship between Agent Builder sessions and deployed workflows, emphasizing that changes made during agent sessions don't automatically affect production deployments until explicitly pushed and redeployed.

Key Changes

  • Added a new tip section explaining that Agent Builder changes are safe to experiment with and won't affect existing deployments
  • Restructured the "Updating a Deployment" section to better explain the decoupled nature of Agent Builder and deployments
  • Clarified the explicit steps required to deploy changes (push to GitHub → update version in LlamaCloud)
  • Added context that this separation allows for safe iteration and experimentation without impacting production

Notable Details

  • The changes emphasize the safety and stability of the deployment model, which should help users understand they can freely experiment in Agent Builder
  • The updated workflow steps are now more explicit about the two-step process: code changes must be pushed to GitHub first, then the deployment must be explicitly updated
  • The documentation now clearly communicates that Agent Builder and production deployments are intentionally decoupled systems

https://claude.ai/code/session_01Rok9AU8XDhhgH1x3FhbhGg

🔄 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/workflows-py/pull/321 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 2/3/2026 **Status:** ✅ Merged **Merged:** 2/3/2026 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `claude/slack-docs-agent-builder-deployment-wsBVW` --- ### 📝 Commits (1) - [`79f1fff`](https://github.com/run-llama/workflows-py/commit/79f1fff461d17e136c1d1929371f73345f3282c6) docs: clarify that Agent Builder changes require explicit redeployment ### 📊 Changes **1 file changed** (+13 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `docs/src/content/docs/llamaagents/cloud/builder.md` (+13 -4) </details> ### 📄 Description ## Summary Updated documentation to clarify the relationship between Agent Builder sessions and deployed workflows, emphasizing that changes made during agent sessions don't automatically affect production deployments until explicitly pushed and redeployed. ## Key Changes - Added a new tip section explaining that Agent Builder changes are safe to experiment with and won't affect existing deployments - Restructured the "Updating a Deployment" section to better explain the decoupled nature of Agent Builder and deployments - Clarified the explicit steps required to deploy changes (push to GitHub → update version in LlamaCloud) - Added context that this separation allows for safe iteration and experimentation without impacting production ## Notable Details - The changes emphasize the safety and stability of the deployment model, which should help users understand they can freely experiment in Agent Builder - The updated workflow steps are now more explicit about the two-step process: code changes must be pushed to GitHub first, then the deployment must be explicitly updated - The documentation now clearly communicates that Agent Builder and production deployments are intentionally decoupled systems https://claude.ai/code/session_01Rok9AU8XDhhgH1x3FhbhGg --- <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 02:17:14 -05:00
yindo closed this issue 2026-02-16 02:17:14 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
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/workflows-py#324
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?