Use git-harness v0.3.1 for non-interactive network git

[bschellenberger2600]

Summary

• Pin github.com/git-fire/git-harness v0.3.1 and delegate PrepareNetworkGit to harness
• Apply non-interactive fetch behavior on default fetch --all, mainline fetch, and full sync paths
• Migrate .goreleaser.stable.yaml from deprecated brews → homebrew_casks
• Fix release workflow gate to verify Casks/git-rain.rb (not Formula/) after Goreleaser publish

Why

Parallel git-rain runs were leaking HTTPS credential prompts when remotes lacked cached credentials. The fix belongs in git-harness (shared with git-fire); git-rain now consumes it.

Supersedes #16 (reverted in #18 after premature merge while Bugbot Autofix was in flight).

Related PRs

• git-harness (merged, v0.3.1): Disable interactive git credential prompts on network operations git-harness#9
• git-fire (consumer tests): Regression tests for non-interactive git network failures git-fire#107
• Revert: Revert PR #16 merge (wait for Bugbot autofix) #18

Test plan

• go test -race -count=1 ./...
• CI green (including Validate GoReleaser Configs)
• Bugbot review clean
• Human review before merge

Made with Cursor

[coderabbitai]

Warning

Review limit reached

@bschellenberger2600, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 55 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5e6da329-322f-440e-8825-7f2d1dc5ae5a

📥 Commits

Reviewing files that changed from the base of the PR and between 96af267 and d4b3b77.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (9)

• .github/workflows/release.yml
• .goreleaser.stable.yaml
• cmd/root.go
• cmd/root_test.go
• go.mod
• internal/git/command.go
• internal/git/command_test.go
• internal/git/fetch_mainline.go
• internal/git/rain.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/non-interactive-git-network

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Did not approve. Cursor Bugbot check passed but no BUGBOT_REVIEW comment was posted, so the required automated review signal is missing. Human review is still needed before merge; no reviewers assigned (solo maintainer repo).

  

_{Sent by Cursor Approval Agent: Pull Request Approver}