run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-08-24 20:01:34 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[PR #276] [CLOSED] make export workflow path relative #282

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/276
Author: @adrianlyjak
Created: 1/13/2026
Status: ❌ Closed

Base: main ← Head: claude/relative-workflow-paths-RGVg8

📝 Commits (3)

  • b612587 feat: add workflow_name and workflow_path to WorkflowGraph
  • dad5eeb chore: add changeset for relative workflow paths feature
  • 45a8ce7 refactor: improve path handling for installed vs local packages

📊 Changes

4 files changed (+151 additions, -5 deletions)

View changed files

➕ .changeset/relative-workflow-paths.md (+5 -0)
📝 packages/llama-index-workflows/src/workflows/representation/build.py (+100 -2)
📝 packages/llama-index-workflows/src/workflows/representation/types.py (+11 -1)
📝 packages/llama-index-workflows/tests/test_representation_utils.py (+35 -2)

📄 Description

Add workflow metadata fields to WorkflowGraph representation:

  • workflow_name: The workflow class name
  • workflow_path: Relative path to the source file (from cwd)

Also make resource node source_file paths relative for consistency.

The paths are converted to relative paths using os.path.relpath() to make them portable and consistent across different environments.

🔄 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/276 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 1/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `claude/relative-workflow-paths-RGVg8` --- ### 📝 Commits (3) - [`b612587`](https://github.com/run-llama/workflows-py/commit/b6125873ae666b39d5bcea3c4ed2502fa41cb013) feat: add workflow_name and workflow_path to WorkflowGraph - [`dad5eeb`](https://github.com/run-llama/workflows-py/commit/dad5eeb878583241d22367d85273ac3f3287e3b0) chore: add changeset for relative workflow paths feature - [`45a8ce7`](https://github.com/run-llama/workflows-py/commit/45a8ce7bffdbe00465f6b996ab64a827135aea6e) refactor: improve path handling for installed vs local packages ### 📊 Changes **4 files changed** (+151 additions, -5 deletions) <details> <summary>View changed files</summary> ➕ `.changeset/relative-workflow-paths.md` (+5 -0) 📝 `packages/llama-index-workflows/src/workflows/representation/build.py` (+100 -2) 📝 `packages/llama-index-workflows/src/workflows/representation/types.py` (+11 -1) 📝 `packages/llama-index-workflows/tests/test_representation_utils.py` (+35 -2) </details> ### 📄 Description Add workflow metadata fields to WorkflowGraph representation: - workflow_name: The workflow class name - workflow_path: Relative path to the source file (from cwd) Also make resource node source_file paths relative for consistency. The paths are converted to relative paths using os.path.relpath() to make them portable and consistent across different environments. --- <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:08 -05:00
yindo closed this issue 2026-02-16 02:17:08 -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#282
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?