What
After PR #31 (fix for #10) merges, re-run the Sync AI Rules workflow in a consumer repo (e.g. laurigates/mcu-tinkering-lab, the repro from #10) and confirm:
rulesync fetch laurigates/.github --path .rulesync pulls the 3 rule files (no 404 / 'No files were fetched')- the fetch guard does not trip
rulesync generate emits configs for all four targets and the sync PR opens in the consumer repo
Why
rulesync fetch pulls from the source repo's main, so the fix is only end-to-end verifiable post-merge. Tracking here instead of a PR-body checklist so it isn't lost once #31 closes.
🤖 Generated with Claude Code
https://claude.ai/code/session_017RvFaUeBffGUoT3ioujtXw
What
After PR #31 (fix for #10) merges, re-run the Sync AI Rules workflow in a consumer repo (e.g. laurigates/mcu-tinkering-lab, the repro from #10) and confirm:
rulesync fetch laurigates/.github --path .rulesyncpulls the 3 rule files (no 404 / 'No files were fetched')rulesync generateemits configs for all four targets and the sync PR opens in the consumer repoWhy
rulesync fetch pulls from the source repo's
main, so the fix is only end-to-end verifiable post-merge. Tracking here instead of a PR-body checklist so it isn't lost once #31 closes.🤖 Generated with Claude Code
https://claude.ai/code/session_017RvFaUeBffGUoT3ioujtXw