Skip to content

fix(ci): dispatch to .git-private-farm, not the nonexistent dot-git-private-farm - #490

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/dispatch-target-nonexistent-repo
Aug 25, 2026
Merged

fix(ci): dispatch to .git-private-farm, not the nonexistent dot-git-private-farm#490
hyperpolymath merged 1 commit into
mainfrom
fix/dispatch-target-nonexistent-repo

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

The bug

.github/workflows/inbox-steward.yml:328 POSTs a repository_dispatch to:

repos/hyperpolymath/dot-git-private-farm/dispatches

hyperpolymath/dot-git-private-farm does not exist — verified gh repo view → 404. The repo is hyperpolymath/.git-private-farm (private, exists).

Why nobody noticed

Two things hid it:

  1. The call is --silent 2>&1 || echo "::warning::Dispatch to .git-private-farm failed" — a 404 degrades to an annotation, never a failed run.
  2. The log strings already say the correct name. The echo and the warning both print .git-private-farm while the API path says dot-git-private-farm. Reading the run log gives you no reason to suspect the target.

cicd-squabbler/.github/workflows/instant-sync.yml:44 already uses the dotted name correctly, which is what made the discrepancy findable.

Impact

This is the first hop of the closed loop documented at the top of .git-private-farm/.github/workflows/inbox-steward-propagate.yml:

gitbot-fleet/inbox-steward → hypatia/inbox-steward-intake → farm/inbox-steward-propagate

The hop has never worked. (This workflow is currently disabled_manually following the 2026-07-20/21 notification burst, so nothing changes behaviourally today — but it would have stayed broken on re-enable.)

hypatia/.github/workflows/inbox-steward-intake.yml:336,338 carries the identical defect; companion PR filed there.

Changes

  • inbox-steward.yml — corrected the dispatch target
  • docs/INBOX-STEWARD-AUTOMATION.adoc — corrected the repo name in the affected-repos list and the runbook cd

Verified: grep -rn dot-git-private-farm returns zero hits in this repo after the change.

🤖 Generated with Claude Code

…rivate-farm

The repository_dispatch POST targeted
repos/hyperpolymath/dot-git-private-farm/dispatches, which returns 404 —
the repo is named .git-private-farm.

The failure was invisible for two reasons: the call is suffixed
`--silent 2>&1 || echo "::warning::..."`, so a 404 degrades to a warning
rather than a failure; and the surrounding log strings already said
".git-private-farm", so reading the run log gave no hint the API path
differed. cicd-squabbler/instant-sync.yml already uses the dotted name.

This severs the first hop of the documented closed loop
(gitbot-fleet/inbox-steward -> hypatia/inbox-steward-intake ->
farm/inbox-steward-propagate). hypatia carries the same defect; fixed in
a companion PR.

Docs updated for the same name.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@gitar-bot

gitar-bot Bot commented Aug 25, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

@hyperpolymath
hyperpolymath merged commit 4f3877a into main Aug 25, 2026
21 of 27 checks passed
@hyperpolymath
hyperpolymath deleted the fix/dispatch-target-nonexistent-repo branch August 25, 2026 14:58
hyperpolymath added a commit to hyperpolymath/hypatia that referenced this pull request Aug 25, 2026
…rivate-farm (#720)

## The bug

`.github/workflows/inbox-steward-intake.yml:338` POSTs to:

```
/repos/hyperpolymath/dot-git-private-farm/dispatches
```

`hyperpolymath/dot-git-private-farm` **does not exist** (`gh repo view`
→ 404). The repo is `hyperpolymath/.git-private-farm`.

## Why it stayed invisible

Identical to the companion defect in `gitbot-fleet` (see
hyperpolymath/gitbot-fleet#490):

1. The call is `>/dev/null 2>&1` with an `::warning::Failed to dispatch
to .git-private-farm` fallback — a 404 never fails the run.
2. **The log line immediately above prints the correct name**: `echo
"Dispatching to .git-private-farm: ..."`. So the run log tells you it
dispatched to `.git-private-farm` while the API path says otherwise.

## Impact

Second hop of the loop documented in
`.git-private-farm/.github/workflows/inbox-steward-propagate.yml`:

```
gitbot-fleet/inbox-steward → hypatia/inbox-steward-intake → farm/inbox-steward-propagate
```

Both the first and second hops target the nonexistent repo, so the
ruleset-update propagation path has never reached the farm.

## Changes

- corrected the dispatch target (line 338)
- corrected the misleading comment (line 336)

Verified: `grep -rn dot-git-private-farm` returns zero hits after the
change.

Companion PR: hyperpolymath/gitbot-fleet#490

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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