Repository navigation
fix(gitops): observe the required Go workflow policy - #644
Conversation
Validation at exact head
Hosted CI, external exact-head review, merge/publication and native reconciliation readback are still pending. This import alone is not a CI performance improvement; #237 still owns the source migration and #565 the consumer cache outcome. |
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
@coderabbitai full review |
✅ Action performedFull review finished. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Walkthrough
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to
|
Readiness at exact head
The source migration and any measured CI/cache improvement remain outside this import, under #237/#565. Promotion and merge still require a fresh ownership, body, head and merge-state check; no security or required gate is waived. |
Why
KSail still runs an older required Go workflow, preventing it from benefiting from the maintained cache policy. Migrating that gate safely first requires a complete view of its existing protections.
What
Add read-only visibility of the existing Go workflow rule without changing which repositories it protects or how merges are gated. Source migration and measured CI improvements remain separate follow-up work.
Part of #643