Conversation
|
Caution Review failedThe pull request is closed. WalkthroughUpdated four GitHub Issue Templates to convert their Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (4)
Comment |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
.github/ISSUE_TEMPLATE/feature.yml (1)
106-106: Add a trailing newline (YAMLlint error).File is missing a newline at EOF; fix to satisfy lint/checkers.
Apply this diff:
projects: - thenarfer/1 +.github/ISSUE_TEMPLATE/sprint-plan.yml (1)
117-117: Add a trailing newline (YAMLlint error).Missing newline at EOF; add one to clear lint.
projects: - thenarfer/1 +.github/ISSUE_TEMPLATE/tech-debt.yml (2)
25-25: Trim stray whitespace.Remove the trailing spaces on this otherwise blank line to keep diffs clean.
- +
77-78: Shorthand project reference approved; add trailing newline.Schema change LGTM; also add a newline at EOF to satisfy lint.
projects: - thenarfer/1 +
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
.github/ISSUE_TEMPLATE/bug.yml(1 hunks).github/ISSUE_TEMPLATE/feature.yml(1 hunks).github/ISSUE_TEMPLATE/sprint-plan.yml(1 hunks).github/ISSUE_TEMPLATE/tech-debt.yml(2 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/ISSUE_TEMPLATE/feature.yml
[error] 106-106: no new line character at the end of file
(new-line-at-end-of-file)
.github/ISSUE_TEMPLATE/sprint-plan.yml
[error] 117-117: no new line character at the end of file
(new-line-at-end-of-file)
.github/ISSUE_TEMPLATE/tech-debt.yml
[error] 78-78: no new line character at the end of file
(new-line-at-end-of-file)
🔇 Additional comments (3)
.github/ISSUE_TEMPLATE/feature.yml (1)
105-106: Shorthand project reference looks good.Switching to
thenarfer/1simplifies maintenance and removes workflow coupling..github/ISSUE_TEMPLATE/bug.yml (1)
42-42: Project mapping → shorthand is correct.
projects: - thenarfer/1is the expected schema; no further changes needed here..github/ISSUE_TEMPLATE/sprint-plan.yml (1)
116-117: Standardized project reference — good move.Consistent with other templates and easier to maintain.
Corrects the schema for the key in issue templates to prevent validation errors and ensure future compatibility. Closes #56
b918567 to
24639d8
Compare

name: "Tech Debt / Chore PR"
about: "Refactor, cleanups, dep bumps, infra chores"
Why now
Risk reduction and maintainability by simplifying project references in issue templates.
Scope
Updated project references in all issue templates (bug, feature, sprint-plan, tech-debt).
Change
thenarfer/1formatValidation
Evidence (before/after, logs, links)
Before:
After:
—
See
docs/DoR.md&docs/DoD.md.Closes #56
Summary by CodeRabbit