Skip to content

GitHub issues updates#24292

Open
akristen wants to merge 2 commits intodocker:mainfrom
akristen:gh-issues
Open

GitHub issues updates#24292
akristen wants to merge 2 commits intodocker:mainfrom
akristen:gh-issues

Conversation

@akristen
Copy link
Contributor

@akristen akristen commented Mar 6, 2026

PR to address 4 GitHub issues assigned to my docs areas.

@akristen akristen self-assigned this Mar 6, 2026
@akristen akristen added area/billing area/accounts Relates to Docker accounts labels Mar 6, 2026
@netlify
Copy link

netlify bot commented Mar 6, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit eacd518
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69aaf3d8c9d60e0007f12952
😎 Deploy Preview https://deploy-preview-24292--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.

@docker-agent
Copy link
Contributor

docker-agent bot commented Mar 6, 2026

PR Review Failed — The review agent encountered an error and could not complete the review. View logs.

@dvdksn
Copy link
Contributor

dvdksn commented Mar 9, 2026

/review

Copy link
Contributor

@docker-agent docker-agent 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

Assessment: 🟡 NEEDS ATTENTION

This PR addresses 4 GitHub issues with updates to billing and SSO documentation. The changes are generally good, with accurate information and appropriate scope. One medium-severity clarity issue was found in the SSO FAQ that should be addressed.

Findings

1 issue found (1 medium)

  • ✅ No critical issues (vendored content, missing redirects)
  • ✅ Content accuracy is good
  • ⚠️ One clarity issue with phrasing

Docker recommends that you contact your identity provider to retrieve a new X.509 certificate, then update the certificate in the [SSO configuration settings](/manuals/enterprise/security/single-sign-on/manage.md#manage-sso-connections) in the Docker Admin Console.

- If your organization doesn't enforce SSO, your users can log in with their username and password credentials.
- If your organization enforces SSO and credentials won't work, then Docker recommends you [contact us](https://app.docker.com/support/contact) for additional support.
Copy link
Contributor

Choose a reason for hiding this comment

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

ISSUE: Awkward phrasing creates confusing logic

The phrase "If your organization enforces SSO and credentials won't work" is redundant and confusing. When SSO is enforced, credentials won't work by definition—this is the expected behavior, not a separate condition.

Suggested fix:

Break this into clearer statements:

- If your organization enforces SSO, username and password credentials won't work. Contact [Docker support](https://app.docker.com/support/contact) for additional help.

Or use parenthetical explanation:

- If your organization enforces SSO (where credentials won't work), contact [Docker support](https://app.docker.com/support/contact) for additional help.

Style note: Per STYLE.md, "Docker recommends you" is meta-commentary that adds little value. Be more direct: "Contact Docker support" instead of "Docker recommends you contact us."

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

Labels

area/accounts Relates to Docker accounts area/billing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants