Repository navigation
chore: document agent workflow and enforce single-line release commits - #24
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe change adds repository guidance for development, validation, and merges. The release-please workflow now uses the pending release PR title as the squash merge subject and sets the merge body to empty. ChangesRelease merge guidance
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to No verified merge-blocking risk remains; the title-format concern requires separate configuration evidence. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches✨ Simplify code
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 |
66ab94e to
0743b95
Compare
|
@greptileai review |
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
Add SDK-specific agent guidance derived from main Devsy, covering the pinned toolchain, generation checks, protocol and process-ownership invariants, idiomatic Go, and current-head CI/review requirements.
Release PR automation now supplies the PR title and an explicitly empty squash body so merged commits remain a single line.
Validation: all prek hooks (including strict Go lint/format and protobuf checks), workflow validation, and diff checks passed. Final-head local CodeRabbit completed with zero findings. All current-head CI checks passed, and Greptile reviewed 0743b95 with confidence 5/5 and no actionable findings. Full remote CodeRabbit review completed on the same head with no actionable comments; no review threads remain. GitHub verified the commit signature as valid.