Skip to content

chore: scheduled workflow to update vendored Effect source#45

Merged
ryanbas21 merged 1 commit into
mainfrom
chore/scheduled-effect-vendor-update
May 13, 2026
Merged

chore: scheduled workflow to update vendored Effect source#45
ryanbas21 merged 1 commit into
mainfrom
chore/scheduled-effect-vendor-update

Conversation

@ryanbas21
Copy link
Copy Markdown
Owner

Summary

  • Adds a daily GitHub Actions workflow (update-effect-vendor.yml) that dispatches pullfrog to run git subtree pull for the vendored Effect repo at repos/effect/
  • Runs at 4:17 AM UTC daily, also supports manual trigger via workflow_dispatch
  • Pullfrog handles the subtree pull, opens a PR on success, or an issue on merge conflicts

Test plan

  • Verify workflow appears in Actions tab after merge
  • Trigger manually via workflow_dispatch to confirm it dispatches pullfrog correctly

🤖 Generated with Claude Code

Adds a GitHub Actions workflow that runs daily at 4:17 AM UTC and
dispatches pullfrog to perform the git subtree pull for repos/effect/.
Also supports manual trigger via workflow_dispatch.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@pullfrog pullfrog Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

Verified the pullfrog workflow interface contract, the subtree pull command, permissions, and edge case handling. No issues found.

TL;DR — Adds a scheduled GitHub Actions workflow that dispatches pullfrog daily to run git subtree pull for the vendored Effect source at repos/effect/.

Key changes

  • Add scheduled vendor-update workflow — New workflow runs daily at 4:17 AM UTC (and supports manual trigger) with actions: write permission to dispatch pullfrog. The prompt covers all three outcomes: no upstream changes (close), clean subtree pull (open PR), merge conflicts (open issue). The git subtree pull command matches the existing documentation in CLAUDE.md.

Summary | 1 file | 1 commit | base: mainchore/scheduled-effect-vendor-update


Scheduled pullfrog dispatch

Before: No automated mechanism to update the vendored Effect source.
After: A daily cron workflow dispatches pullfrog to run git subtree pull and either opens a PR or an issue depending on the outcome.

The workflow correctly uses the actions/github-script@v7 action to call createWorkflowDispatch on pullfrog.yml with the prompt and name inputs — matching the pullfrog workflow interface at .github/workflows/pullfrog.yml:6-12. The permission scope is appropriately minimal: only actions: write is granted, which is the minimum required for createWorkflowDispatch. The prompt handles all three post-pull scenarios explicitly.

.github/workflows/update-effect-vendor.yml

Pullfrog  | View workflow run𝕏

Copy link
Copy Markdown
Contributor

@pullfrog pullfrog Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No new issues found.

TL;DR — Adds a scheduled GitHub Actions workflow that dispatches pullfrog daily at 4:17 AM UTC to run git subtree pull for the vendored Effect repo at repos/effect/. Also supports manual trigger.

Key changes

  • Add daily workflow to update vendored Effect source — New .github/workflows/update-effect-vendor.yml uses actions/github-script@v7 to dispatch pullfrog.yml with a prompt that handles three outcomes: closes silently when no upstream changes, opens a PR on successful pull, and opens an issue on merge conflicts.

Summary | 1 file | 1 commit | base: mainchore/scheduled-effect-vendor-update

Pullfrog  | View workflow run𝕏

@ryanbas21 ryanbas21 merged commit 8d88982 into main May 13, 2026
1 check passed
@ryanbas21 ryanbas21 deleted the chore/scheduled-effect-vendor-update branch May 13, 2026 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant