run-llama/template-workflow-data-extraction
1
0
Fork 0
mirror of https://github.com/run-llama/template-workflow-data-extraction.git synced 2026-07-16 04:03:31 -04:00
Code Issues Packages Projects Releases Wiki Activity

[PR #5] [MERGED] Start adding some CI and dev utilities here #5

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/template-workflow-data-extraction/pull/5
Author: @adrianlyjak
Created: 7/29/2025
Status: ✅ Merged
Merged: 7/29/2025
Merged by: @adrianlyjak

Base: main ← Head: adrian/template-test

📝 Commits (10+)

📊 Changes

42 files changed (+1703 additions, -17 deletions)

View changed files

➕ .github/workflows/check-regeneration.yml (+26 -0)
➕ .gitignore (+6 -0)
📝 .gitignore.jinja (+0 -1)
📝 copier.yaml (+3 -1)
➕ copier/copy_utils.py (+271 -0)
📝 pyproject.toml.jinja (+19 -2)
📝 src/{{ project_name_snake }}/export_types.py (+2 -0)
📝 src/{{ project_name_snake }}/process_file.py (+1 -1)
➕ test-proj/.env.template (+6 -0)
📝 test-proj/.gitignore (+2 -2)
➕ test-proj/README.md (+58 -0)
➕ test-proj/copier.yaml (+26 -0)
➕ test-proj/llama_deploy.local (+25 -0)
➕ test-proj/llama_deploy.yaml (+24 -0)
➕ test-proj/pyproject.toml (+47 -0)
➕ test-proj/src/test_proj/__init__.py (+0 -0)
➕ test-proj/src/test_proj/config.py (+70 -0)
➕ test-proj/src/test_proj/export_types.py (+81 -0)
➕ test-proj/src/test_proj/process_file.py (+221 -0)
➕ test-proj/src/test_proj/schemas.py (+7 -0)

...and 22 more files

📄 Description

It's difficult to develop this template. You need to generate it, make changes, then push those changes back to the template. I've been using a test-proj folder for this, and thought it would be better to formalize this process as we start depending on this template more.

This change:

  • checks in the materialized test-proj code to the repo
  • adds a utility script that can
    • validate that the test-proj is up to date, by blowing it away and regenerating it and checking for changes
    • push changes from the materialized code to the template, and give you warnings about files that need to be manually merged
    • it also starts adding type check, linting, and formatting. This should facilitate easier merges and consistency as the templates get updated.

Right now this just checks that the regeneration is up to date. Waiting to fix the format and type errors until some other changes are merged in

🔄 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/template-workflow-data-extraction/pull/5 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 7/29/2025 **Status:** ✅ Merged **Merged:** 7/29/2025 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `adrian/template-test` --- ### 📝 Commits (10+) - [`f23ccdc`](https://github.com/run-llama/template-workflow-data-extraction/commit/f23ccdca1959aab3d02b6698a0e3b0120760db72) feat: adding some template tests to make sure everything is kosher - [`3e6a0e6`](https://github.com/run-llama/template-workflow-data-extraction/commit/3e6a0e690081dffdeb2e6d78297d08b6f70f5e72) commit the generated project for change tracking - [`74ccd39`](https://github.com/run-llama/template-workflow-data-extraction/commit/74ccd39890e9bae93e244a04d958f2e3b2228b36) adding dependencies - [`c25d37e`](https://github.com/run-llama/template-workflow-data-extraction/commit/c25d37e7fab687ab7aca75079f0f00daa31b3357) regenerate - [`d53b53a`](https://github.com/run-llama/template-workflow-data-extraction/commit/d53b53ace6063ff1fe56474383997eafda90c191) wip typecheck and format checks - [`76c37e5`](https://github.com/run-llama/template-workflow-data-extraction/commit/76c37e5df288f103e48506d4e7504732f6a74463) start validation script - [`a3351bb`](https://github.com/run-llama/template-workflow-data-extraction/commit/a3351bbbb85fcff8664c41d1bfa8149bf043f12d) update check generated - [`c3eafa5`](https://github.com/run-llama/template-workflow-data-extraction/commit/c3eafa5450d53091f202346bfde7ca7645c2102f) wip - [`4b311ff`](https://github.com/run-llama/template-workflow-data-extraction/commit/4b311ff6fbd6b76a13a25bece5c3b5fe1825ed82) wip - [`23d2c97`](https://github.com/run-llama/template-workflow-data-extraction/commit/23d2c978e68ea0b86cad2c1882458bad579339b3) improve ### 📊 Changes **42 files changed** (+1703 additions, -17 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/check-regeneration.yml` (+26 -0) ➕ `.gitignore` (+6 -0) 📝 `.gitignore.jinja` (+0 -1) 📝 `copier.yaml` (+3 -1) ➕ `copier/copy_utils.py` (+271 -0) 📝 `pyproject.toml.jinja` (+19 -2) 📝 `src/{{ project_name_snake }}/export_types.py` (+2 -0) 📝 `src/{{ project_name_snake }}/process_file.py` (+1 -1) ➕ `test-proj/.env.template` (+6 -0) 📝 `test-proj/.gitignore` (+2 -2) ➕ `test-proj/README.md` (+58 -0) ➕ `test-proj/copier.yaml` (+26 -0) ➕ `test-proj/llama_deploy.local` (+25 -0) ➕ `test-proj/llama_deploy.yaml` (+24 -0) ➕ `test-proj/pyproject.toml` (+47 -0) ➕ `test-proj/src/test_proj/__init__.py` (+0 -0) ➕ `test-proj/src/test_proj/config.py` (+70 -0) ➕ `test-proj/src/test_proj/export_types.py` (+81 -0) ➕ `test-proj/src/test_proj/process_file.py` (+221 -0) ➕ `test-proj/src/test_proj/schemas.py` (+7 -0) _...and 22 more files_ </details> ### 📄 Description It's difficult to develop this template. You need to generate it, make changes, then push those changes back to the template. I've been using a test-proj folder for this, and thought it would be better to formalize this process as we start depending on this template more. This change: - checks in the materialized test-proj code to the repo - adds a utility script that can - validate that the test-proj is up to date, by blowing it away and regenerating it and checking for changes - push changes from the materialized code to the template, and give you warnings about files that need to be manually merged - it also starts adding type check, linting, and formatting. This should facilitate easier merges and consistency as the templates get updated. Right now this just checks that the regeneration is up to date. Waiting to fix the format and type errors until some other changes are merged in --- <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:16:38 -05:00
yindo closed this issue 2026-02-16 03:16:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
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/template-workflow-data-extraction#5
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?