Skip to content

Update CONTRIBUTING.md#29

Closed
Ashusf90 wants to merge 1 commit into
Codelab-Davis:mainfrom
Ashusf90:main
Closed

Update CONTRIBUTING.md#29
Ashusf90 wants to merge 1 commit into
Codelab-Davis:mainfrom
Ashusf90:main

Conversation

@Ashusf90
Copy link
Copy Markdown

@Ashusf90 Ashusf90 commented Apr 29, 2026

Pull Request

Summary

Describe the change and the user or maintainer outcome.

Linked context

Closes # or Related to # or Supersedes #

Checklist

  • I ran the relevant local checks.
  • I updated documentation or confirmed no docs changes were needed.
  • I linked related issues or pull requests and confirmed this is not duplicate work.
  • This change stays within the stated scope of the PR.
  • I wrote this change myself and did not use AI or agent tools to create commits, open the pull request, or generate substantial code/docs for this PR.

Notes for reviewers

Call out any tradeoffs, follow-up work, or setup needed to validate the change.

Summary by CodeRabbit

  • Documentation
    • Updated contributor guidelines with example PR descriptions for documentation-only changes, including formatting verification instructions.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 29, 2026

📝 Walkthrough

Walkthrough

This pull request adds a new documentation section to CONTRIBUTING.md that provides a concrete example of a PR description for documentation-only changes, including typical doc modifications and a formatting verification command.

Changes

Cohort / File(s) Summary
Documentation Examples
CONTRIBUTING.md
Added example PR description for doc-only changes with enumerated doc-related change types and pnpm format:prettier:check verification command.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

Poem

🐰 A doc so clear, a guide so fine,
With examples bright, contributors align,
Format and check, the path is set,
Contributing wisdom we won't forget! 📝✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The PR title 'Update CONTRIBUTING.md' is vague and generic, using non-descriptive language that doesn't convey what specific change was made. Consider a more specific title like 'Add example PR description for doc-only changes' to clearly indicate the main purpose of the change.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Review rate limit: 2/3 reviews remaining, refill in 20 minutes.

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

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

@github-actions
Copy link
Copy Markdown

This pull request needs a small update before review:

  • PR titles must follow Conventional Commit style, for example feat: add project overview.
  • Pull requests must complete every checklist item in the template.
  • Add linked context such as Closes #123, Related to #123, or Supersedes #123 in the PR template.

@github-actions github-actions Bot added needs: title A pull request title does not meet the repository title standard. area: docs Project documentation and contributor guidance. kind: docs Documentation-only changes or issues. and removed needs: title A pull request title does not meet the repository title standard. labels Apr 29, 2026
@github-actions github-actions Bot requested a review from CodeLabDavis April 29, 2026 08:22
@github-actions github-actions Bot added needs: compliance The author or reporter needs to fix template or policy gaps. needs: linked-context A pull request needs a linked issue or related pull request. needs: title A pull request title does not meet the repository title standard. labels Apr 29, 2026
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CONTRIBUTING.md (1)

320-353: ⚠️ Potential issue | 🟡 Minor

This section doesn’t match the stated PR-template objective.

The added content is an example PR description, but it does not provide the reusable template structure described in this PR’s objective (Summary, Linked context, Checklist, Notes for reviewers). Please replace this example block with an actual template contributors can copy directly.

Suggested replacement
-## Example: First Pull Request (Docs Change)
-
-Below is a sample pull request description for a small documentation update.
-
----
-
-### Title
-docs: improve contributing guide with clarification on setup steps (`#XX`)
-
----
-
-### Summary
-This PR improves the contributing documentation by clarifying the project setup steps for new contributors.
-
----
-
-### Linked Issue
-Closes `#XX`
-
----
-
-### Changes
-- Updated setup instructions in `CONTRIBUTING.md`
-- Fixed minor wording issues for clarity
-- Improved formatting for readability
-
----
-
-### Verification
-Run the following command to ensure formatting is correct:
-
-```bash
-pnpm format:prettier:check
-```
+## Pull request template
+
+### Summary
+Describe what changed and what outcome this creates for users/maintainers.
+
+### Linked context
+- Closes #...
+- Related to #...
+- Supersedes #...
+
+### Checklist
+- [ ] I ran relevant local checks.
+- [ ] I updated docs if behavior or workflow changed.
+- [ ] I linked related issues/PRs.
+- [ ] This PR is scoped to one clear objective.
+- [ ] I confirm this PR is human-authored and follows repo authorship policy.
+
+### Notes for reviewers
+Call out tradeoffs, follow-up work, or setup needed to validate this change.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 320 - 353, Replace the example PR description
block under "Example: First Pull Request (Docs Change)" with a reusable,
copyable PR template titled "Pull request template" that includes the headings
"Summary", "Linked context", "Checklist", and "Notes for reviewers"; remove the
broken/trailing code fence and stray shell snippet and ensure the "Verification"
step shows the correct formatted command (pnpm format:prettier:check) as a code
block; make the template content match the suggested replacement sections and
checklist items so contributors can copy-paste directly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 349-352: Replace the non-canonical docs formatting command string
"pnpm format:prettier:check" with the canonical docs-only command "pnpm
format:check" so the CONTRIBUTING.md uses a single consistent formatting
command; update the occurrence in the paragraph that currently reads "Run the
following command to ensure formatting is correct:" and ensure any example block
or inline mention matches the "pnpm format:check" token.

---

Outside diff comments:
In `@CONTRIBUTING.md`:
- Around line 320-353: Replace the example PR description block under "Example:
First Pull Request (Docs Change)" with a reusable, copyable PR template titled
"Pull request template" that includes the headings "Summary", "Linked context",
"Checklist", and "Notes for reviewers"; remove the broken/trailing code fence
and stray shell snippet and ensure the "Verification" step shows the correct
formatted command (pnpm format:prettier:check) as a code block; make the
template content match the suggested replacement sections and checklist items so
contributors can copy-paste directly.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0e095ffe-5a4a-4a33-8bf5-bbd496c486c9

📥 Commits

Reviewing files that changed from the base of the PR and between 8854ec8 and 22bfc30.

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

Comment thread CONTRIBUTING.md
Comment on lines +349 to +352
Run the following command to ensure formatting is correct:

```bash
pnpm format:prettier:check
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Use the same docs-formatting command already documented above.

Line 352 uses pnpm format:prettier:check, while the canonical docs-only command in this file is pnpm format:check (Line 233). Keep one command to avoid contributor confusion.

Suggested fix
-Run the following command to ensure formatting is correct:
+Run the following command to ensure formatting is correct:
 
 ```bash
-pnpm format:prettier:check
+pnpm format:check
</details>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
Run the following command to ensure formatting is correct:

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 349 - 352, Replace the non-canonical docs
formatting command string "pnpm format:prettier:check" with the canonical
docs-only command "pnpm format:check" so the CONTRIBUTING.md uses a single
consistent formatting command; update the occurrence in the paragraph that
currently reads "Run the following command to ensure formatting is correct:" and
ensure any example block or inline mention matches the "pnpm format:check"
token.

@phongndo phongndo closed this Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Project documentation and contributor guidance. kind: docs Documentation-only changes or issues. needs: compliance The author or reporter needs to fix template or policy gaps. needs: linked-context A pull request needs a linked issue or related pull request. needs: title A pull request title does not meet the repository title standard.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants