chore(ci): retarget umbrella dispatch + docs to constructorfabric - #158
Conversation
|
Warning Review limit reached
More reviews will be available in 39 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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. 📝 WalkthroughWalkthroughThis PR replaces ChangesOrganization Repository References
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The cross-repo umbrella chart-publish workflow now lives in
`constructorfabric/insight` (was `cyberfabric/cyber-insight`). Update
docker.yml's `create-github-app-token` owner/repositories and the
`gh workflow run --repo` target accordingly, plus the README links.
Image push target is unaffected — docker.yml uses
`${{ github.repository }}`, which auto-resolves once the repo moves
to the new org.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Anton Zelenov <antonz@constructor.tech>
a6375e8 to
191489a
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
1-211:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winNote: CODEOWNERS still references the old organization.
While the README links have been updated to
constructorfabric, the.github/CODEOWNERSfile still assigns reviews to@cyberfabric/securityand@cyberfabric/insight-app-maintainersteams. After the repository moves, these team references may need updating to ensure PR review routing works correctly.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@README.md` around lines 1 - 211, The CODEOWNERS entry still references the old org teams (`@cyberfabric/security` and `@cyberfabric/insight-app-maintainers`); update the CODEOWNERS file to point to the new organization’s team handles so PR review routing works after the repo move. Edit CODEOWNERS, find the lines containing `@cyberfabric/security` and `@cyberfabric/insight-app-maintainers` and replace them with the corresponding `@constructorfabric/`<team> (or whatever the new org team names are), then commit the change and verify GitHub recognizes the new team handles.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@README.md`:
- Around line 1-211: The CODEOWNERS entry still references the old org teams
(`@cyberfabric/security` and `@cyberfabric/insight-app-maintainers`); update the
CODEOWNERS file to point to the new organization’s team handles so PR review
routing works after the repo move. Edit CODEOWNERS, find the lines containing
`@cyberfabric/security` and `@cyberfabric/insight-app-maintainers` and replace them
with the corresponding `@constructorfabric/`<team> (or whatever the new org team
names are), then commit the change and verify GitHub recognizes the new team
handles.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: af582908-89c8-4cc4-8106-8818ea156756
📒 Files selected for processing (2)
.github/workflows/docker.ymlREADME.md
@cyberfabric/security and @cyberfabric/insight-app-maintainers no longer resolve after the org rename — without this the review-routing rules silently skip PRs in the new org. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Anton Zelenov <antonz@constructor.tech>
5484f85 to
a68e693
Compare
1 participant
Summary
docker.yml's cross-repo dispatch to target the renamed umbrella repoconstructorfabric/insight(wascyberfabric/cyber-insight):create-github-app-tokenowner/repositories +gh workflow run --repo.docker.ymluses${{ github.repository }}, which auto-resolves toghcr.io/constructorfabric/insight-frontonce the repo lives in the new org.2 files changed, 12 insertions / 12 deletions.
Test plan
ghcr.io/constructorfabric/insight-front:<tag>constructorfabric/insightCompanion PR: constructorfabric/insight#1270
🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Chores