Repository navigation
Conversation
WalkthroughThe workflow file is updated with elevated permissions and a new step that automatically posts Docker image details and registry links as comments on associated pull requests or commits after the build completes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested reviewers
Pre-merge checks✅ Passed checks (3 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📥 Commits
Reviewing files that changed from the base of the PR and between 3f1d3a3 and c1f10ddcc0ca82b951d6e288dfeb3a0124c03b91.
📒 Files selected for processing (2)
.github/workflows/build-docker-images.yaml(2 hunks).github/workflows/docker-dev-images.yaml(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
- GitHub Check: llm_evals
- GitHub Check: build (3.10)
- GitHub Check: build (3.12)
- GitHub Check: build (3.11)
- GitHub Check: build
🔇 Additional comments (3)
.github/workflows/build-docker-images.yaml (1)
13-15: Permission updates are appropriate for the new comment functionality.The changes enable the workflow to post comments:
contents: writeis required forrepos.createCommitCommentAPIpull-requests: writeis required forissues.createCommentAPI on PRs.github/workflows/docker-dev-images.yaml (2)
13-15: Permission updates are appropriate for the new comment functionality.The changes enable the workflow to post comments:
contents: writeis required forrepos.createCommitCommentAPIpull-requests: writeis required forissues.createCommentAPI on PRs
58-104: Well-implemented comment step with appropriate PR lookup logic.The implementation correctly:
- Extracts branch and commit information from the context
- Constructs registry links for both full SHA and short SHA tags
- Uses proper line break escaping (
.join('\n')on line 79)- Searches for open PRs matching the branch name, which is appropriate for a push workflow
- Falls back to commit comments when no PR exists
|
Dev Docker images are ready for this commit:
Use either tag to pull the image for testing. |
|
Dev Docker images are ready for this commit:
Use either tag to pull the image for testing. |
|
Dev Docker images are ready for this commit:
Use either tag to pull the image for testing. |
Signed-off-by: Robusta Runner <aantny@gmail.com>
Signed-off-by: Robusta Runner <aantny@gmail.com>
1. Add runbook alerts to runbook prompts so llm will be able to select it. 2. Remove old alert runbook fetching as part of invesigation 3. Add eval for alert with multiple relevant runbooks due to matching alert - Test report here: https://www.braintrust.dev/app/robustadev/p/HolmesGPT/experiments/root-master-k%3D165_-20251218_145120?c= 4. Removed responses logs that spammed test logs. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit # Release Notes * **New Features** * Enhanced runbook matching to include alert-based matching in addition to symptom-based matching, improving runbook discovery accuracy. * Added alerts metadata to runbook catalog entries for better runbook relevance filtering. * **Chores** * Simplified investigation workflow by streamlining instruction data flow. * Improved test coverage with new integration test for multi-runbook alert scenarios. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Mohse Morad <moshemorad12340@gmail.com> Signed-off-by: Robusta Runner <aantny@gmail.com>
58d1c0c to
727e133
Compare
…workflows-in-holmes-re
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.github/workflows/docker-dev-images.yaml (1)
58-104: Implementation is correct; consider handling multiple PRs and comment duplication.The logic correctly handles both PR and commit scenarios with appropriate API calls. The
headparameter format${owner}:${branch}is valid for filtering PRs.Two minor considerations for a production workflow:
Multiple PRs from same branch: If multiple open PRs exist from the same branch (each targeting different bases), only the first receives a comment. While unlikely in typical workflows, consider logging or commenting on all matching PRs if needed.
Duplicate comments: Each push creates a new comment without checking for existing ones. With frequent commits, this generates noise. Consider updating an existing recent comment or checking for duplicates before posting.
These are refinements for robustness and don't block the current implementation.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📥 Commits
Reviewing files that changed from the base of the PR and between c1f10ddcc0ca82b951d6e288dfeb3a0124c03b91 and acd14d0.
📒 Files selected for processing (1)
.github/workflows/docker-dev-images.yaml(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
- GitHub Check: build (3.11)
- GitHub Check: build (3.12)
- GitHub Check: build (3.10)
- GitHub Check: llm_evals
- GitHub Check: build
🔇 Additional comments (1)
.github/workflows/docker-dev-images.yaml (1)
12-15: Reconsidercontents: writepermission for commit comments.The
pull-requests: writepermission is correctly needed for PR comments. However,contents: writeallows broader repository modifications. GitHub's documentation is unclear about which permission is actually required forrepos.createCommitComment—some sources indicate it works without explicit permissions, while others confirmcontents: writeis necessary. Consider testing whether this workflow actually requirescontents: write, or alternatively, limit commenting to pull requests only (which requires onlypull-requests: write).
|
Dev Docker images are ready for this commit:
Use either tag to pull the image for testing. |
|
Dev Docker images are ready for this commit:
Use either tag to pull the image for testing. |
## Summary - add automated comments to dev docker build workflow with links to built images - add automated comments to release docker build workflow with links to built images and tags - adjust workflow permissions to allow posting comments on PRs or commits ## Testing - not run (not needed for workflow changes) ------ [Codex Task](https://chatgpt.com/codex/tasks/task_b_6947d623f1a8832797c92848985d3af4) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated CI/CD workflows to automatically post Docker image build details and registry links as comments on pull requests or commits. Comments provide full and short image tags along with registry information upon image release. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Robusta Runner <aantny@gmail.com> Signed-off-by: Mohse Morad <moshemorad12340@gmail.com> Co-authored-by: moshemorad <moshemorad12340@gmail.com> Signed-off-by: Filip Grebowski <grebowskifilip@gmail.com>
Summary
Testing
Codex Task
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.