Skip to content

chore(ci): automate fork sync, janitor, and CLI releases - #1

Merged
benjaminshafii merged 1 commit into
devfrom
chore/fork-sync-janitor
Feb 16, 2026
Merged

benjaminshafii merged 1 commit into
devfrom
chore/fork-sync-janitor

Conversation

@benjaminshafii

@benjaminshafii benjaminshafii commented Feb 16, 2026 •

Copy link
Copy Markdown
Member

Summary

  • add fork-sync-upstream workflow to regularly rebase the fork patch branch on upstream dev, open/update a sync PR, and label conflicts for repair.
  • add fork-janitor workflow that detects conflicted/failing sync PRs, attempts automated repair with opencode run (OpenAI-backed), pushes fixes, and updates labels/comments.
  • add release-cli-fork workflow that publishes fork CLI assets for tags like v1.1.60-openwork.2.

Defaults / knobs

  • FORK_PATCH_BRANCH (default: feat/hot-reload-smooth)
  • FORK_UPSTREAM_BRANCH (default: dev)
  • FORK_SYNC_BASE_BRANCH (default: dev)
  • FORK_JANITOR_MODEL (default: openai/gpt-4.1)

Required secret

  • OPENAI_API_KEY (used by fork-janitor)

Notes

  • workflows run on ubuntu-latest to avoid depending on upstream custom runners.
  • sync PRs are labeled fork-sync, and conflict cases get sync-conflict + janitor-needed.

@github-actions

Copy link
Copy Markdown

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

@benjaminshafii
benjaminshafii merged commit 994123d into dev Feb 16, 2026
4 of 7 checks passed
@benjaminshafii
benjaminshafii deleted the chore/fork-sync-janitor branch February 16, 2026 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant