Skip to content

Add image link comments to docker workflows - #1210

Merged
aantn merged 4 commits into
masterfrom
codex/linear-mention-rob-26-update-github-workflows-in-holmes-re
Dec 21, 2025
Merged

aantn merged 4 commits into
masterfrom
codex/linear-mention-rob-26-update-github-workflows-in-holmes-re

Conversation

@aantn

@aantn aantn commented Dec 21, 2025 •

Copy link
Copy Markdown
Collaborator

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

Summary by CodeRabbit

  • Chores
    • Improved CI/CD workflow to automatically post Docker image details and registry links in pull request and commit comments.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai

coderabbitai Bot commented Dec 21, 2025 •

Copy link
Copy Markdown
Contributor

Walkthrough

The 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

Cohort / File(s) Summary
Workflow permissions and Docker image commenting
\.github/workflows/docker-dev-images\.yaml
Updated workflow permissions: contents permission changed from read to write; added pull-requests permission with write access. Added new "Comment with image details" step using actions/github-script@v7 that constructs Docker image tags, derives repo metadata (owner, repo, branch, sha), fetches open PRs for the current branch, and posts a comment with image tags and registry link to either the associated PR or directly to the commit.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify that the updated workflow permissions (contents:write, pull-requests:write) are appropriate and minimally sufficient
  • Validate the script logic for constructing short and long image tags, registry URL formation, and PR/commit detection
  • Confirm proper error handling and logging output

Possibly related PRs

  • HolmesGPT/holmesgpt#964: Implements the initial Docker build-and-push workflow that this PR enhances with post-build commenting functionality.

Suggested reviewers

  • moshemorad

Pre-merge checks

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding automated image link comments to Docker workflows.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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: write is required for repos.createCommitComment API
  • pull-requests: write is required for issues.createComment API 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: write is required for repos.createCommitComment API
  • pull-requests: write is required for issues.createComment API 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

Comment thread .github/workflows/build-docker-images.yaml Outdated
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@aantn
aantn requested a review from moshemorad December 21, 2025 13:05
@github-actions

Copy link
Copy Markdown
Contributor

aantn and others added 3 commits December 21, 2025 20:03
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>
@aantn
aantn force-pushed the codex/linear-mention-rob-26-update-github-workflows-in-holmes-re branch from 58d1c0c to 727e133 Compare December 21, 2025 18:03
@aantn
aantn enabled auto-merge (squash) December 21, 2025 18:05

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 head parameter format ${owner}:${branch} is valid for filtering PRs.

Two minor considerations for a production workflow:

  1. 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.

  2. 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: Reconsider contents: write permission for commit comments.

The pull-requests: write permission is correctly needed for PR comments. However, contents: write allows broader repository modifications. GitHub's documentation is unclear about which permission is actually required for repos.createCommitComment—some sources indicate it works without explicit permissions, while others confirm contents: write is necessary. Consider testing whether this workflow actually requires contents: write, or alternatively, limit commenting to pull requests only (which requires only pull-requests: write).

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Results of HolmesGPT evals

  • ask_holmes: 31/37 test cases were successful, 2 regressions, 1 setup failures, 3 mock failures
Test suite Test case Status
ask 01_how_many_pods ✅
ask 02_what_is_wrong_with_pod ✅
ask 04_related_k8s_events ✅
ask 05_image_version ✅
ask 09_crashpod ✅
ask 10_image_pull_backoff ✅
ask 110_k8s_events_image_pull ✅
ask 11_init_containers ✅
ask 13a_pending_node_selector_basic ✅
ask 14_pending_resources ✅
ask 15_failed_readiness_probe ✅
ask 163_compaction_follow_up ✅
ask 17_oom_kill ❌
ask 18_oom_kill_from_issues_history ❌
ask 19_detect_missing_app_details ✅
ask 20_long_log_file_search ✅
ask 24_misconfigured_pvc ✅
ask 24a_misconfigured_pvc_basic ✅
ask 28_permissions_error 🚧
ask 39_failed_toolset ✅
ask 41_setup_argo ✅
ask 42_dns_issues_steps_new_tools ✅
ask 43_current_datetime_from_prompt ✅
ask 45_fetch_deployment_logs_simple ✅
ask 51_logs_summarize_errors ✅
ask 53_logs_find_term ✅
ask 54_not_truncated_when_getting_pods ✅
ask 59_label_based_counting ✅
ask 60_count_less_than ✅
ask 61_exact_match_counting ✅
ask 63_fetch_error_logs_no_errors ✅
ask 79_configmap_mount_issue ✅
ask 83_secret_not_found ✅
ask 86_configmap_like_but_secret ✅
ask 93_calling_datadog[0] 🔧
ask 93_calling_datadog[1] 🔧
ask 93_calling_datadog[2] 🔧

Legend

  • ✅ the test was successful
  • :minus: the test was skipped
  • ⚠️ the test failed but is known to be flaky or known to fail
  • 🚧 the test had a setup failure (not a code regression)
  • 🔧 the test failed due to mock data issues (not a code regression)
  • 🚫 the test was throttled by API rate limits/overload
  • ❌ the test failed and should be fixed before merging the PR

@aantn
aantn merged commit af8b2a5 into master Dec 21, 2025
10 of 11 checks passed
@aantn
aantn deleted the codex/linear-mention-rob-26-update-github-workflows-in-holmes-re branch December 21, 2025 18:24
FilipGrebowski pushed a commit to FilipGrebowski/holmesgpt that referenced this pull request Dec 27, 2025
## 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>
@coderabbitai coderabbitai Bot mentioned this pull request Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants