fix: use Homebrew tap app bot identity - #18
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Homebrew tap updater now commits with a tap-specific bot identity. The test verifies the configured Git user name and noreply email. ChangesHomebrew tap bot identity
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized change makes generated Homebrew tap commits use the intended GitHub App bot identity and adds assertions for both author settings. No actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Makes generated tap commits use the x52-homebrew-tap-updater GitHub App bot identity.
The previous release-bot noreply address associates commits with an unrelated ordinary GitHub user. The new address uses the App bot numeric user ID and login, which GitHub resolves to the App bot.
Adds fixture assertions for both Git author settings.
Validated with nix develop -c just check.
Summary by CodeRabbit