Skip to content

docs: rename to Docker Agent Action and sync README#230

Open
Sayt-0 wants to merge 2 commits into
mainfrom
docs/rename-to-docker-agent-action
Open

docs: rename to Docker Agent Action and sync README#230
Sayt-0 wants to merge 2 commits into
mainfrom
docs/rename-to-docker-agent-action

Conversation

@Sayt-0
Copy link
Copy Markdown
Member

@Sayt-0 Sayt-0 commented Jun 4, 2026

Summary

  • Rename title to Docker Agent Action and update uses: / issue links to docker/docker-agent-action (repo is being renamed)
  • Sync the inputs/outputs tables with action.yml
  • Fix broken links

Changes

Inputs added: skip-summary, org-membership-token, auth-org, skip-auth
Outputs added: cagent-version, security-blocked, input-risk-level
Fixed: prompt-suspicious description; Security Policy now points to .github/SECURITY.md; removed dead Discussions link (Discussions disabled on the repo)

- Rename title to 'Docker Agent Action' and update repo references to docker/docker-agent-action
- Add missing inputs (skip-summary, org-membership-token, auth-org, skip-auth)
- Add missing outputs (cagent-version, security-blocked, input-risk-level)
- Fix prompt-suspicious description (content is stripped, not just detected)
- Fix broken links: point Security Policy to .github/SECURITY.md, remove disabled Discussions link
Copy link
Copy Markdown
Contributor

@docker-agent docker-agent left a comment

Choose a reason for hiding this comment

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

Assessment: 🟢 APPROVE

This is a clean documentation-only PR. All changes in README.md were reviewed against the source of truth (action.yml) and confirmed correct:

  • Action rename — all 7 uses: docker/cagent-action@VERSION references correctly updated to docker/docker-agent-action@VERSION
  • Outputs table — all 10 outputs from action.yml are present and accurately described (exit-code, output-file, cagent-version, mcp-gateway-installed, execution-time, verbose-log-file, security-blocked, secrets-detected, prompt-suspicious, input-risk-level) ✅
  • New inputsskip-summary, org-membership-token, auth-org, skip-auth descriptions match action.yml
  • prompt-suspicious description — updated wording matches action.yml exactly ✅
  • Link fixessecurity/README.md.github/SECURITY.md (file confirmed to exist), issues URL updated to docker/docker-agent-action, dead Discussions link removed ✅

No issues found in the changed code.

Comment thread README.md
- **Prompt Injection Detection**: Warns about suspicious patterns in user prompts
- **Automatic Incident Response**: Creates security issues and fails workflows when secrets are detected

See [security/README.md](security/README.md) for complete security documentation.
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.

I would suggest merging #228 first, it's the "real" security doc that was accidentally removed in a previous PR

Comment thread README.md Outdated
Comment on lines +120 to +122
| `org-membership-token` | PAT with `read:org` scope for org membership authorization checks | No | - |
| `auth-org` | GitHub organization to check membership against (used with `org-membership-token`) | No | - |
| `skip-auth` | Skip the built-in authorization check (when the caller already performed its own) | No | `false` |
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.

I don't think we need to include these. The top two are deprecated and the last one should only be used internally by the PR review workflow

…puts

- Point Security Policy links to SECURITY.md (the doc restored in #228)
- Remove org-membership-token/auth-org (deprecated) and skip-auth
  (internal PR-review-workflow use only) from the inputs table
@Sayt-0
Copy link
Copy Markdown
Member Author

Sayt-0 commented Jun 4, 2026

Thx @derekmisler! I fixed the Security Policy links to point to SECURITY.md and I removed the auth inputs from the table. i think we can now merge #228

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants