Fix nested code fences in aws-well-architected-review issue template (#2449)

The issue-body template was wrapped in a three-backtick fence while
containing three-backtick HCL and Bash blocks, so the HCL example's
closing fence terminated the wrapper early and the following fence
swallowed the remaining workflow sections. Use a four-backtick wrapper
so the nested blocks render intact.

Co-authored-by: Aaron Powell <me@aaron-powell.com>
This commit is contained in:
Adrien Clerbois
2026-07-28 03:25:36 +02:00
committed by GitHub
parent 7dc152f472
commit b94ae92ab0
+2 -2
View File
@@ -119,7 +119,7 @@ Label with "well-architected" and the pillar name (e.g., "security", "reliabilit
**Title**: `[WAF-<PILLAR>] [Brief Finding] — [Risk Level]` **Title**: `[WAF-<PILLAR>] [Brief Finding] — [Risk Level]`
**Body**: **Body**:
```markdown ````markdown
## 🏗️ Well-Architected Finding: [Brief Title] ## 🏗️ Well-Architected Finding: [Brief Title]
**Pillar**: [Name] | **Risk Level**: [High/Medium/Low] | **Effort**: [Low/Medium/High] **Pillar**: [Name] | **Risk Level**: [High/Medium/Low] | **Effort**: [Low/Medium/High]
@@ -158,7 +158,7 @@ aws s3api put-bucket-encryption --bucket <name> \
- [ ] Security Hub finding resolved (if applicable) - [ ] Security Hub finding resolved (if applicable)
**Well-Architected Question**: [WAF question this maps to] **Well-Architected Question**: [WAF question this maps to]
``` ````
### Step 7: Create EPIC Tracking Issue ### Step 7: Create EPIC Tracking Issue
Label with "well-architected" and "epic". Label with "well-architected" and "epic".