-
Notifications
You must be signed in to change notification settings - Fork 256
GCP v9 release blog post #16027
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
GCP v9 release blog post #16027
Conversation
280b24a
to
104d4ef
Compare
Your site preview for commit 2f04d9e is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16027-2f04d9e3.s3-website.us-west-2.amazonaws.com. |
Pull Request ReviewThis blog post announcing GCP v9 has good structure and content, but there are several issues that need to be addressed: Critical IssuesMissing newline at end of file (line 88): The blog post file must end with a newline per repository standards. Broken link (line 45): The Oracle Database link is missing the protocol - should be https://www.pulumi.com/registry/packages/gcp/api-docs/oracledatabase instead of pulumi.com/registry/packages/gcp/api-docs/oracledatabase. Duplicate image reference (lines 79, 88): The same image code-suggestion.png is referenced twice. The second reference (line 88) should likely be migration-prompt.png based on the context about Neo opening a pull request. Spelling error (line 68): "improvemetns" should be "improvements". Style IssuesHeading capitalization (line 32): "In Case You missed It - New Modules" should follow sentence case per style guide: "In case you missed it - new modules". Heading capitalization (line 44): "Model armor" should be "Model Armor" (proper noun capitalization for product names). Heading capitalization (line 60): "Increased field validation" should be "Increased Field Validation" to match the style of the preceding heading. Content SuggestionsDate inconsistency: The frontmatter shows date as 2025-09-17, but since this is about a current release, verify this date is accurate. Image descriptions: Consider adding more descriptive alt text for the screenshot images to improve accessibility. Call to action: The post would benefit from a clearer call-to-action section at the end encouraging readers to try the new version. Minor IssuesThe post structure and content are generally good, with clear sections and helpful links. The Neo integration example is particularly valuable for users looking to upgrade. Please address these issues, particularly the critical ones, before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great 💯 thank you
Your site preview for commit feb02a4 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16027-feb02a4b.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 2d3f770 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16027-2d3f7703.s3-website.us-west-2.amazonaws.com. |
Blog post to announce GCP v9
Adds upgrade example using Neo