RunicGateway/link
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

ci(docs): auto-sync PROJECT_TREE.md to the docs repo on push to main #16

Merged
whitlocktech merged 1 commits from chore/sync-project-tree-ci into main 2026-07-22 21:20:45 +00:00
Conversation 1 Commits 1 Files Changed 2 +165
wtclaude commented 2026-07-22 21:19:57 +00:00
Member
Copy Link

Adds a sync-project-tree workflow that keeps link/PROJECT_TREE.md in RunicGateway/docs current.

Behavior

  • Trigger: push to main (+ manual workflow_dispatch).
  • Regenerates the tree from git ls-files via .gitea/scripts/gen_tree.py (deterministic: directories first, then case-insensitive name).
  • Clones the docs repo, writes link/PROJECT_TREE.md, and if it changed, force-pushes branch chore/sync-link-tree and opens a PR against docs main (reuses the open PR if one already exists). Never touches docs main directly.
  • Auth reuses the existing REGISTRY_USER / REGISTRY_TOKEN secrets (the token needs read/write on RunicGateway/docs).

Companion to docs PR #41, which seeds the initial PROJECT_TREE.md files. The first run of this workflow may open a small follow-up PR normalizing the tree to the generator's exact output (dropping the archive-style link-main/ root wrapper from the seed).

🤖 AI-assisted (Claude). Disclosed per org policy.

Co-Authored-By: Claude noreply@anthropic.com

Adds a `sync-project-tree` workflow that keeps `link/PROJECT_TREE.md` in [`RunicGateway/docs`](https://gitea.whitlocktech.com/RunicGateway/docs) current. ## Behavior - **Trigger:** push to `main` (+ manual `workflow_dispatch`). - Regenerates the tree from `git ls-files` via `.gitea/scripts/gen_tree.py` (deterministic: directories first, then case-insensitive name). - Clones the docs repo, writes `link/PROJECT_TREE.md`, and if it changed, force-pushes branch `chore/sync-link-tree` and opens a PR against docs `main` (reuses the open PR if one already exists). **Never touches docs `main` directly.** - Auth reuses the existing `REGISTRY_USER` / `REGISTRY_TOKEN` secrets (the token needs read/write on `RunicGateway/docs`). Companion to docs PR #41, which seeds the initial `PROJECT_TREE.md` files. The first run of this workflow may open a small follow-up PR normalizing the tree to the generator's exact output (dropping the archive-style `link-main/` root wrapper from the seed). 🤖 AI-assisted (Claude). Disclosed per org policy. Co-Authored-By: Claude <noreply@anthropic.com>
wtclaude added 1 commit 2026-07-22 21:19:58 +00:00
ci(docs): auto-sync PROJECT_TREE.md to the docs repo on push to main ecdaf9171b 
Add a sync-project-tree workflow that regenerates this repo's tracked-file
tree and opens (or force-updates) a PR against RunicGateway/docs whenever the
layout on main changes. Never writes to the docs repo's main directly. Reuses
the existing REGISTRY_USER / REGISTRY_TOKEN secrets. Tree rendering lives in
.gitea/scripts/gen_tree.py (deterministic, dirs-first ordering).

Co-Authored-By: Claude <noreply@anthropic.com>
whitlocktech approved these changes 2026-07-22 21:20:37 +00:00
whitlocktech merged commit 7e4177c6c0 into main 2026-07-22 21:20:45 +00:00
whitlocktech deleted branch chore/sync-project-tree-ci 2026-07-22 21:20:46 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
whitlocktech
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ksfixitman whitlocktech wtclaude
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RunicGateway/link#16
No description provided.
Delete Branch "chore/sync-project-tree-ci"

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?