Skip to content

fix: correct PR template reference path in CLAUDE.md - #2022

Merged
ashleyshaw merged 1 commit into
developfrom
fix/claude-md-reference-path
Aug 18, 2026
Merged

fix: correct PR template reference path in CLAUDE.md#2022
ashleyshaw merged 1 commit into
developfrom
fix/claude-md-reference-path

Conversation

@ashleyshaw

@ashleyshawashleyshaw commented Aug 18, 2026

Copy link
Copy Markdown
Member

Linked issues

Fixes#2003

Context

  • Severity/Impact: Low
  • Affected versions/environments: All

Root Cause

Incorrect reference path in CLAUDE.md pointing to non-existent location for PR template.

Fix Summary

Updated CLAUDE.md line 360 to correctly reference the PR template at .github/PULL_REQUEST_TEMPLATE/FEEDBACK_RESPONSE.md instead of the incorrect PULL_REQUEST_TEMPLATE/FEEDBACK_RESPONSE.md (missing .github/ prefix).

Verification

  • Repository structure complies with CLAUDE.md rules
  • References updated to match actual file paths
  • All related issues are linked

Changelog

Added

(None)

Changed

  • Corrected PR template file path reference in CLAUDE.md

Fixed

  • Fixed incorrect .github/ prefix in CLAUDE.md reference for PR template location

Removed

(None)


Checklist (Global DoD / PR)

  • All AC met and demonstrated
  • Tests added/updated (unit/E2E as appropriate)
  • Accessibility checklist completed (where relevant):
    • N/A - Documentation only
  • Docs/readme/changelog updated (if user-facing)
  • Security checklist completed (where relevant):
    • N/A - Documentation reference fix only
  • Code/design reviews approved

@coderabbitai

coderabbitaiBot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in:9 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 3beab638-2516-45ef-804a-dc8dc03e3694

📥 Commits

Reviewing files that changed from the base of the PR and between 7467d13 and 8263c3b.

📒 Files selected for processing (1)
  • CLAUDE.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actionsBot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

🚫 This PR description is missing required template content.

Missing required section(s): Changelog

Please update the PR body using one of the repository PR templates:

Empty placeholders, unchecked checklist boxes, and stub issue references do not count.

@github-actions

github-actionsBot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

⏱️ Aging and SLA annotation

  • Age: 0 day(s)
  • SLA state: Within SLA
  • Thresholds: warn at 7 days, breach at 14 days
  • Last updated: 2026-08-18T15:03:33.189Z

Maintained by project-meta-sync workflow.

@github-actionsgithub-actionsBot added status:needs-review Awaiting code review type:bug Bug or defect priority:normal Default priority area:documentation Docs & guides lang:md Markdown content/docs type:chore Chore / small hygiene change meta:needs-changelog Requires a changelog entry before merge labels Aug 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔗 Project Linking Validation

Projects Checked: 57
Projects with Links: 56

✅ All projects have Related Issues sections

Detailed issue link validation is deferred to Phase 4.


Validation Date: 2026-08-18T14:42:41.338Z
Validator: GitHub Actions

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Reviewer Summary for PR #2022

CI Status:success
Files changed: 1
Risk Distribution: 0 critical, 0 high, 0 medium, 1 low

Recommendations

  • Ready to proceed pending human review

@ashleyshaw
ashleyshaw enabled auto-merge (squash) August 18, 2026 15:02
@github-actionsgithub-actionsBot removed the type:chore Chore / small hygiene change label Aug 18, 2026
Fixed incorrect reference from 'PULL_REQUEST_TEMPLATE/FEEDBACK_RESPONSE.md' to
'.github/PULL_REQUEST_TEMPLATE/FEEDBACK_RESPONSE.md' (missing '.github/' prefix).
This aligns with CLAUDE.md repository structure rules which require GitHub-native
governance files to be stored in '.github/', not at the root level.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@ashleyshaw
ashleyshawforce-pushed the fix/claude-md-reference-path branch from b0818eb to 8263c3bCompareAugust 18, 2026 16:21
@ashleyshaw
ashleyshaw merged commit 6d3bc0b into developAug 18, 2026
23 of 28 checks passed
@ashleyshaw
ashleyshaw deleted the fix/claude-md-reference-path branch August 18, 2026 16:24
@github-actions

Copy link
Copy Markdown
Contributor

🔗 Project Linking Validation

Projects Checked: 57
Projects with Links: 57

✅ All projects have Related Issues sections

Detailed issue link validation is deferred to Phase 4.


Validation Date: 2026-08-18T16:28:57.121Z
Validator: GitHub Actions

@github-actions

Copy link
Copy Markdown
Contributor

Milestone Allocation

✅ 2026-08-18T16:35:39.932Z [main] Starting allocation...
✅ 2026-08-18T16:35:40.451Z [main] Allocating PR #2022...
✅ 2026-08-18T16:35:41.948Z [allocate-pr] Allocated PR #2022 to milestone #76
✅ 2026-08-18T16:35:42.402Z [main] Allocating 1 linked issue(s)...
⏭️ 2026-08-18T16:35:42.730Z [allocate-issue] Issue #2003 already allocated to milestone #76
✅ 2026-08-18T16:35:42.730Z [summary] Allocation complete. | Allocated: 1 PR(s), 0 issue(s) | Skipped: 1 | Errors: 0

@ashleyshawashleyshaw self-assigned this Aug 18, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:documentationDocs & guideslang:mdMarkdown content/docsmeta:needs-changelogRequires a changelog entry before mergepriority:normalDefault prioritystatus:needs-reviewAwaiting code reviewtype:bugBug or defect

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: failing tests in scripts/automation/__tests__/auto-update-all.test.js

1 participant

@ashleyshaw