Skip to content

ci: use docker/cagent-action/.github/workflows/review-pr.yml#24132

Open
dvdksn wants to merge 1 commit intodocker:mainfrom
dvdksn:use-cagent-review-action
Open

ci: use docker/cagent-action/.github/workflows/review-pr.yml#24132
dvdksn wants to merge 1 commit intodocker:mainfrom
dvdksn:use-cagent-review-action

Conversation

@dvdksn
Copy link
Contributor

@dvdksn dvdksn commented Feb 11, 2026

@netlify
Copy link

netlify bot commented Feb 11, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 44692cc
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6990ac088ba7a70008341792
😎 Deploy Preview https://deploy-preview-24132--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions bot added area/release Relates to CI or deployment ci ci updates labels Feb 11, 2026
@dvdksn dvdksn requested a review from derekmisler February 11, 2026 14:55
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Review Summary

Workflow refactoring looks good! ✅

This PR successfully migrates from an inline agent configuration to using the reusable workflow from docker/cagent-action. The configuration is clear and well-structured with no documentation quality issues found.

The additional-prompt parameter appropriately configures the review agent with clear instructions and guidelines. The content is technically accurate and suitable for its purpose as agent configuration.

Copy link

@derekmisler derekmisler left a comment

Choose a reason for hiding this comment

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

the only reason i haven't approved this yet is because we need this one to land first, or the prompt files will be ignored

@thaJeztah
Copy link
Member

@dvdksn could we make it aware of pages being removed, and for those to check if a correct redirect is added? i.e., to prevent things like #23949 (comment)

@thaJeztah
Copy link
Member

I think we were also looking at (or already have?) helping with triage; for 404 reports, it could also check wayback-machine to verify if it was a page that previously existed to exclude reports for made-up links 🤔 (if I'm not sure, I usually do a quick check to see if there was anything at that URL in the first place #23949 (comment))

@dvdksn
Copy link
Contributor Author

dvdksn commented Feb 14, 2026

@thaJeztah yes that would be a good addition. Let me update the instruction 👍

@dvdksn
Copy link
Contributor Author

dvdksn commented Feb 14, 2026

@thaJeztah for 404 - yes, for the triage agent (todo) we could probably just add a tool to check the wayback api, eg: https://archive.org/wayback/available?url=docs.docker.com/engine/reference/builder

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
@dvdksn dvdksn force-pushed the use-cagent-review-action branch from f3b26ff to 44692cc Compare February 14, 2026 17:08
@dvdksn dvdksn requested a review from a team February 14, 2026 17:08
@dvdksn dvdksn requested a review from derekmisler February 14, 2026 17:08
Copy link
Member

@usha-mandya usha-mandya left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Relates to CI or deployment ci ci updates status/review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants