Skip to content

TEST: Validate docs for integration-aws #1803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

karenzone
Copy link
Contributor

@karenzone karenzone commented Feb 10, 2025

DO NOT MERGE

This is a TEST PR to validate updated doc content for:

Test status

TEST IN PROGRESS. DO NOT MERGE

What's up?

#1802 is failing. Evidence points to changes in this PR. I'm using the hints from this issue to:

  • validate assumptions
  • illustrate how developers can use this approach to avoid merging bad docs content. (Requires testing content for all changed source files. I did just one here as an example.)

Copy link
Contributor

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

@karenzone
Copy link
Contributor Author

Ugh. The asciidoc migration warning is preventing the error message(s) I'm trying to surface from coming through.

Screenshot 2025-02-10 at 5 45 20 PM

@karenzone
Copy link
Contributor Author

karenzone commented Feb 10, 2025

Retesting with asciidoc warning notification removed.

UPDATE: Looks like a new PR is required to clear that check status.

@karenzone
Copy link
Contributor Author

run docs-build

@karenzone karenzone closed this Feb 12, 2025
@karenzone karenzone deleted the TEST-aws-integration branch February 12, 2025 19:05
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.

1 participant