Fix missing quotes in template vars

[Resonance1584]

Summary by CodeRabbit

• Documentation
  • Updated AWS Account ID formatting in installation documentation examples to consistently use quoted strings in CLI and YAML configuration samples.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Oct 31, 2025 5:30pm

[coderabbitai]

Walkthrough

Documentation updates to add proper quoting around the AWSAccountID value in two configuration examples. The change converts unquoted numeric scalars to quoted strings in both a CLI command example and a YAML variable file, ensuring consistent string type handling across different input methods.

Changes

Cohort / File(s)	Change Summary
Documentation Updates docs/2.0/docs/pipelines/installation/addingexistingrepo.mdx	AWSAccountID values changed from unquoted to quoted strings in two locations: CLI example (AWSAccountID=123456789012 → AWSAccountID="123456789012") and YAML example (AWSAccountID: 123456789012 → AWSAccountID: "123456789012")

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Straightforward formatting corrections
• Documentation-only changes with no code logic modifications
• Consistent, repetitive pattern applied in two locations

Suggested reviewers

• ZachGoldberg

Poem

🔤 A number sat bare, needing quotes to be fair,
In docs where the config lives free,
From scalar to string, what a difference it'll bring—
Proper parsing for all to agree! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "Fix missing quotes in template vars" directly and accurately describes the main changes in the pull request. The changeset adds quotes around AWSAccountID values in two locations within the documentation (a CLI example and a YAML configuration file), which is precisely what the title conveys. The title is concise, specific, and uses clear language that would help a teammate quickly understand the nature of the fix when scanning commit history.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Resonance1584-patch-4

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8d5befa and b4a114d.

📒 Files selected for processing (1)

• docs/2.0/docs/pipelines/installation/addingexistingrepo.mdx (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

docs/**/*.mdx

📄 CodeRabbit inference engine (.cursor/rules/gitlab-background.mdc)

Whenever presenting information that diverges between GitHub and GitLab, use the and components to distinguish the two sets of information UNLESS the distinction is just changing one word. For example, GitHub has pull requests and GitLab has merge requests, so we can just say '... pull/merge requests...' and not need full .

Files:

• docs/2.0/docs/pipelines/installation/addingexistingrepo.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Validate generated content
• GitHub Check: validate_build

🔇 Additional comments (2)

docs/2.0/docs/pipelines/installation/addingexistingrepo.mdx (2)

266-277: Good catch on the quotes for account IDs in CLI examples.

Adding quotes around the AWSAccountID value ensures Boilerplate receives it as a string rather than a numeric value. This prevents any unintended type coercion and maintains consistency with how AWS account IDs should be handled throughout the pipeline configuration.

---

281-288: Excellent fix for YAML type handling.

Quoting the AWSAccountID value in the YAML file ensures the YAML parser correctly interprets it as a string. This is critical since unquoted numeric values could be coerced to numbers, potentially causing issues downstream. The change mirrors the CLI fix above and maintains consistency across both input methods.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}