Recued
Menu
← Back to recipes

Git repo change watch

by recued-core v3 15 views

Use “Git repo change watch” in Recued. A scheduled worktree watch for one trusted local Git repository path.

How it works 5 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (5 steps)
◆ changed_files recued-core.git.repo.changed_files
Changed files repo on git
■ has_changes compare
Check if changed files stdout has data
◆ status recued-core.git.repo.status
Status repo on git
skip: step.has_changes not_equal true
◆ recent_commits recued-core.git.repo.log_recent
Log recent repo on git
skip: step.has_changes not_equal true
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

end hour setting = 18
repo dir setting = [object Object]
weekdays setting = 1,2,3,4,5
start hour setting = 8
commit limit setting = 5

Uses (4 operations)

Triggers Time watch core.watch.time
Pack operation Changed files repo on git recued-core.git.repo.changed_files
Pack operation Status repo on git recued-core.git.repo.status
Pack operation Log recent repo on git recued-core.git.repo.log_recent

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Read Triggers core.watch.time read-only

3 more aren't listed here. You'll see them at install.

Data it touches

SurfacesTriggers

About

Tags

gitrepositorydeveloperworktreewatchscheduletriggerlocal-clipack:git

Details

5 steps 5 configurable settings recipe_id: git-repo-change-watch