Skip to content

fix(upstream-sync): write notifications to $WORKSPACE/results/ not repo root - #33

Merged
amkunte merged 1 commit into
local-mainfrom
fix/upstream-sync-workspace-path
May 22, 2026
Merged

amkunte merged 1 commit into
local-mainfrom
fix/upstream-sync-workspace-path

Conversation

@amkunte

@amkunte amkunte commented May 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • notify() in sync.sh wrote relative to \$REPO_DIR; Telegram bridge polls \$SUTANDO_WORKSPACE/results/ — notifications silently dropped
  • Fix resolves workspace path from \$SUTANDO_WORKSPACE (with ~ expansion) or ~/.sutando/workspace/ fallback
  • Discovered when 8:07 AM sync fast-forwarded 79 upstream commits but push rejected (missing workflow GitHub scope); failure notification was written to \$REPO_DIR/results/ where no bridge polls

Test plan

  • Run bash skills/upstream-sync/scripts/sync.sh and verify notification appears in ~/.sutando/workspace/results/
  • Confirm Telegram bridge delivers the notification

🤖 Generated with Claude Code

…epo root

notify() was writing relative to \$REPO_DIR; Telegram bridge polls
\$SUTANDO_WORKSPACE/results/ — so push-failure and success notifications
were silently dropped and never delivered to the owner.

Fix resolves WORKSPACE from \$SUTANDO_WORKSPACE (with ~ expansion) or
~/.sutando/workspace/ as fallback, matching the pattern in workspace_default.py.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ghost
ghost merged commit a1c58b3 into local-main May 22, 2026
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