Skip to content

chore: trailing whitespace cleanup#727

Merged
ashleyshaw merged 2 commits into
developfrom
codex/whitespace-cleanup
Jun 1, 2026
Merged

chore: trailing whitespace cleanup#727
ashleyshaw merged 2 commits into
developfrom
codex/whitespace-cleanup

Conversation

@ashleyshaw
Copy link
Copy Markdown
Member

Summary\n- remove trailing whitespace across tracked documentation/text files\n- no semantic content changes intended\n- keep scope limited to formatting hygiene\n\n## Validation\n- ✅ npm run validate:agents\n- ⚠️ npm run validate:frontmatter (fails with pre-existing repo-level warnings/errors not introduced by this change)\n- ⚠️ project git hooks fail in this environment on pre-existing markdownlint/test issues; commit/push used HUSKY=0 to publish this scoped cleanup\n\n## Notes\n- whitespace-only cleanup to reduce noise and unblock future lint/check runs

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 1, 2026

Warning

Review limit reached

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

More reviews will be available in 9 minutes and 33 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro

Run ID: a76d2ab7-4e6d-46b1-b2cc-6d60b5511448

📥 Commits

Reviewing files that changed from the base of the PR and between d69e77b and b4d8af2.

📒 Files selected for processing (108)
  • .github/FOOTER_REMEDIATION_GUIDE.md
  • .github/PULL_REQUEST_TEMPLATE/pr_bug.md
  • .github/PULL_REQUEST_TEMPLATE/pr_chore.md
  • .github/PULL_REQUEST_TEMPLATE/pr_ci.md
  • .github/PULL_REQUEST_TEMPLATE/pr_dep_update.md
  • .github/PULL_REQUEST_TEMPLATE/pr_docs.md
  • .github/PULL_REQUEST_TEMPLATE/pr_feature.md
  • .github/PULL_REQUEST_TEMPLATE/pr_hotfix.md
  • .github/PULL_REQUEST_TEMPLATE/pr_refactor.md
  • .github/PULL_REQUEST_TEMPLATE/pr_release.md
  • .github/SAVED_REPLIES/community/contribution-thanks.md
  • .github/SAVED_REPLIES/issues/duplicate.md
  • .github/SAVED_REPLIES/issues/inactive-issue.md
  • .github/SAVED_REPLIES/issues/needs-reproduction.md
  • .github/SAVED_REPLIES/technical/code-style.md
  • .github/SAVED_REPLIES/technical/performance.md
  • .github/SAVED_REPLIES/technical/security.md
  • .github/SAVED_REPLIES/workflow/draft-pr.md
  • .github/instructions/.archive/saved-replies.instructions.md
  • .github/metrics/out/frontmatter-metrics.md
  • .github/projects/PLANNING_TEMPLATE.md
  • .github/projects/active/AUDIT_PROMPT_README.md
  • .github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md
  • .github/projects/active/ISSUE_35_INSTRUCTION_AUDIT_SUMMARY.md
  • .github/projects/active/template-enforcement-governance/ACTIONS.md
  • .github/projects/active/template-enforcement-governance/ISSUES.md
  • .github/projects/active/wave-5-documentation-audit/INDEX.md
  • .github/projects/active/wave-5-documentation-audit/children/01-2-audit-report-issue-creation.md
  • .github/projects/active/wave-5-documentation-audit/children/03-2-pr-creation-docs.md
  • .github/projects/active/wave-5-documentation-audit/children/03-3-labeling-docs.md
  • .github/projects/active/wave-5-documentation-audit/children/03-4-file-organization-alignment.md
  • .github/projects/active/wave-5-documentation-audit/execution/wave-5-3-phase-2-execution-plan.md
  • .github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md
  • .github/projects/active/wceu-2026/PARENT_ISSUE.md
  • .github/projects/active/wceu-2026/WCEU-01-notebooklm-sources-index.md
  • .github/projects/active/wceu-2026/WCEU-02-commit-profile-photo.md
  • .github/projects/archived/portable-ai-plugin-restructure/portable-ai-plugin-restructure-baseline-command-output-2026-05-15.txt
  • .github/projects/completed/ISSUE_33_BRANDING_AGENT_PARENT_SPEC.md
  • .github/projects/completed/ISSUE_46_TEMPLATE_DESIGN.md
  • .github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md
  • .github/projects/completed/ISSUE_49_SCHEMA_CONFIG_IMPLEMENTATION.md
  • .github/projects/completed/PLANNING_SUMMARY_2026-05-28.md
  • .github/projects/completed/branding-meta-agent-planning-2026-05-28.md
  • .github/projects/completed/wave-4-continuous-monitoring.md
  • .github/prompts/normalize-docs-labels.prompt.md
  • .github/pull_request_template.md
  • .github/reports/audits/issue-creation-docs-audit-report.md
  • .github/reports/audits/issue-types-alignment-audit-2026-06-01.md
  • .github/reports/audits/label-color-consistency-audit-2026-06-01.md
  • .github/reports/audits/workflow-standards-audit-2026-05-31.md
  • .github/reports/mermaid-audit/audit-log.md
  • .github/reports/mermaid-audit/audit-report-2026-05-28.md
  • .github/reports/mermaid-diagram-audit.md
  • .github/reports/wave-4c-remediation-plan.md
  • .github/reports/wave-5-4-readme-discovery-audit.md
  • .github/reports/wave-5-completion-summary.md
  • BRANDING_AGENT_USAGE.md
  • BRANDING_CONFIG_SPEC.md
  • agents/testing.agent.md
  • ai/AUDIT-SUMMARY.md
  • ai/README.md
  • ai/improvement-plan-planner-reviewer.md
  • cookbook/spec-driven-workflow-example.md
  • docs/AUDIT_PR_DOCS_663.md
  • docs/AUTOMATION.md
  • docs/BRANCHING_STRATEGY.md
  • docs/ISSUE_FIELDS.md
  • docs/LABEL_COLOR_STRATEGY.md
  • docs/LABEL_INVENTORY.md
  • docs/LABEL_STRATEGY.md
  • docs/README.md
  • docs/index.md
  • instructions/a11y.instructions.md
  • instructions/issues.instructions.md
  • instructions/pull-requests.instructions.md
  • instructions/self-explanatory-code-commenting.instructions.md
  • scripts/README.md
  • scripts/agents/__tests__/README.md
  • scripts/create-release-pr.cjs
  • skills/design-md-agent/pdfs/js/__tests__/installDeps.test.js
  • wceu-2026/ACCESSIBILITY_AUDIT.md
  • wceu-2026/EXECUTION_MATERIALS_INDEX.md
  • wceu-2026/EXECUTION_PLAN.md
  • wceu-2026/FILE_UPDATE_AUDIT.md
  • wceu-2026/FINAL_REVIEW_CHECKLIST.md
  • wceu-2026/PHASE1_COMPLETION_REPORT.md
  • wceu-2026/PHASE2_EXECUTION.md
  • wceu-2026/PHASE2_EXECUTION_CHECKLIST.md
  • wceu-2026/PHASE2_NOTEBOOKLM_PROMPTS.md
  • wceu-2026/PHASE2_QUICK_START.md
  • wceu-2026/PHASE3_EXECUTION.md
  • wceu-2026/PLANNING.md
  • wceu-2026/README.md
  • wceu-2026/ROLLOUT_PLAN_60_DAYS.md
  • wceu-2026/SLIDES_GENERATION_PROMPT.md
  • wceu-2026/SLIDES_INDEX.md
  • wceu-2026/SPEAKER_NOTES_TEMPLATE.md
  • wceu-2026/VISUAL_DESIGN_SPECIFICATIONS.md
  • wceu-2026/WORDPRESS_INTEGRATION_ROADMAP.md
  • wceu-2026/WORDPRESS_INTEGRATION_SLIDE.md
  • wceu-2026/agent-slides/CONTRIBUTING_GUIDELINES_SLIDES.md
  • wceu-2026/agent-slides/DEVELOPER_EXPERIENCE_AND_BEST_PRACTICES_SLIDES.md
  • wceu-2026/notebooklm/deep-research-prompt.md
  • wceu-2026/notebooklm/sources-index.md
  • wceu-2026/references/glossary.md
  • wceu-2026/talk-outline-25min.md
  • wceu-2026/wceu-talk-june-2026.md
  • workflows/weekly-governance-sync.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/whitespace-cleanup

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 and usage tips.

@github-actions github-actions Bot added area:a11y Accessibility-focused work area:documentation Docs & guides area:tests Test suites & harnesses area:scripts Scripts & tooling lang:md Markdown content/docs status:needs-review Awaiting code review priority:normal Default priority type:chore Chore / small hygiene change labels Jun 1, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

🔍 Reviewer Summary for PR #727

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

Recommendations

  • ⚠️ Security-sensitive files modified (review carefully)
  • ⚠️ Large deletion detected (>500 lines removed)

@github-actions github-actions Bot added the meta:needs-changelog Requires a changelog entry before merge label Jun 1, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request performs formatting cleanups across numerous Markdown files and scripts, primarily by removing trailing whitespace. The reviewer correctly identified that removing trailing double spaces in Markdown files (such as FOOTER_REMEDIATION_GUIDE.md, PLANNING_TEMPLATE.md, and others) breaks intended line breaks, causing separate lines to merge when rendered. The reviewer provided actionable suggestions to use backslashes to preserve these line breaks cleanly without relying on trailing whitespace. All review comments are valid and should be kept.

Comment on lines +460 to +461
**Created**: 2026-05-28
**Status**: Active guidance for footer remediation
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Removing the trailing double spaces from these lines will cause them to merge into a single paragraph when rendered in Markdown. In Markdown, trailing double spaces are syntactically significant as they represent a line break. To preserve the line breaks without relying on trailing whitespace, use a backslash (\\) at the end of each line.

Suggested change
**Created**: 2026-05-28
**Status**: Active guidance for footer remediation
**Created**: 2026-05-28\\\n**Status**: Active guidance for footer remediation\\

Comment on lines +16 to +18
**Created:** YYYY-MM-DD
**Status:** Planning / In Progress / Completed
**Owner:** @username
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Removing the trailing double spaces from these lines will cause them to merge into a single paragraph when rendered in Markdown. In Markdown, trailing double spaces are syntactically significant as they represent a line break. To preserve the line breaks without relying on trailing whitespace, use a backslash (\\) at the end of each line.

Suggested change
**Created:** YYYY-MM-DD
**Status:** Planning / In Progress / Completed
**Owner:** @username
**Created:** YYYY-MM-DD\\\n**Status:** Planning / In Progress / Completed\\\n**Owner:** @username\\

Comment on lines +10 to +16
**Title**: WCEU 2026 Talk Preparation — Finalize 25-Minute Presentation
**Type**: Epic/Parent Issue
**Priority**: Critical
**Status**: Active
**Due Date**: May 31, 2026 (48 hours)
**Talk Date**: June 5–6, 2026
**Assignee**: Ash Shaw
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Removing the trailing double spaces from these lines will cause them to merge into a single paragraph when rendered in Markdown. In Markdown, trailing double spaces are syntactically significant as they represent a line break. To preserve the line breaks without relying on trailing whitespace, use a backslash (\\) at the end of each line.

Suggested change
**Title**: WCEU 2026 Talk Preparation — Finalize 25-Minute Presentation
**Type**: Epic/Parent Issue
**Priority**: Critical
**Status**: Active
**Due Date**: May 31, 2026 (48 hours)
**Talk Date**: June 5–6, 2026
**Assignee**: Ash Shaw
**Title**: WCEU 2026 Talk Preparation — Finalize 25-Minute Presentation\\\n**Type**: Epic/Parent Issue\\\n**Priority**: Critical\\\n**Status**: Active\\\n**Due Date**: May 31, 2026 (48 hours)\\\n**Talk Date**: June 5–6, 2026\\\n**Assignee**: Ash Shaw\\

Comment thread docs/LABEL_INVENTORY.md
Comment on lines +27 to +29
**Version**: v1.1.0
**Created**: 2026-05-31
**Last Updated**: 2026-06-01
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Removing the trailing double spaces from these lines will cause them to merge into a single paragraph when rendered in Markdown. In Markdown, trailing double spaces are syntactically significant as they represent a line break. To preserve the line breaks without relying on trailing whitespace, use a backslash (\\) at the end of each line.

Suggested change
**Version**: v1.1.0
**Created**: 2026-05-31
**Last Updated**: 2026-06-01
**Version**: v1.1.0\\\n**Created**: 2026-05-31\\\n**Last Updated**: 2026-06-01\\

Comment on lines +18 to +21
**Parent Issue:** #651 (Documentation Consolidation)
**Child Issue:** #662 (Issue Creation Docs Consolidation)
**Audited:** 2026-05-31
**Auditor:** Claude Code
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Removing the trailing double spaces from these lines will cause them to merge into a single paragraph when rendered in Markdown. In Markdown, trailing double spaces are syntactically significant as they represent a line break. To preserve the line breaks without relying on trailing whitespace, use a backslash (\\) at the end of each line.

Suggested change
**Parent Issue:** #651 (Documentation Consolidation)
**Child Issue:** #662 (Issue Creation Docs Consolidation)
**Audited:** 2026-05-31
**Auditor:** Claude Code
**Parent Issue:** #651 (Documentation Consolidation)\\\n**Child Issue:** #662 (Issue Creation Docs Consolidation)\\\n**Audited:** 2026-05-31\\\n**Auditor:** Claude Code\\

@github-actions github-actions Bot added the lang:js JavaScript/TypeScript label Jun 1, 2026
@ashleyshaw ashleyshaw merged commit d0fa1e8 into develop Jun 1, 2026
13 of 19 checks passed
@ashleyshaw ashleyshaw deleted the codex/whitespace-cleanup branch June 1, 2026 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:a11y Accessibility-focused work area:documentation Docs & guides area:scripts Scripts & tooling area:tests Test suites & harnesses lang:js JavaScript/TypeScript lang:md Markdown content/docs meta:needs-changelog Requires a changelog entry before merge priority:normal Default priority status:needs-review Awaiting code review type:chore Chore / small hygiene change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant