Skip to content

Add PR template#380

Open
mason-sharp wants to merge 1 commit intomainfrom
task/pr-template
Open

Add PR template#380
mason-sharp wants to merge 1 commit intomainfrom
task/pr-template

Conversation

@mason-sharp
Copy link
Member

PR template to be filled out with each PR in the future.

@coderabbitai
Copy link

coderabbitai bot commented Mar 6, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 675011ae-3f63-42c5-ad8a-2bd42ce26925

📥 Commits

Reviewing files that changed from the base of the PR and between f1c2d4e and 879f170.

📒 Files selected for processing (1)
  • .github/pull_request_template.md

📝 Walkthrough

Walkthrough

Adds a new GitHub pull request template at .github/pull_request_template.md that provides structured sections (Summary, Changes, Testing, Checklist, Notes for Reviewers) and includes Conventional Commits guidance. The file is documentation only and does not modify executable code or runtime behavior.

Changes

Cohort / File(s) Summary
Pull Request Template
.github/pull_request_template.md
New PR template added with sections for Summary, Changes, Testing, Checklist, and Notes for Reviewers; includes Conventional Commits examples and reviewer guidance. File is documentation-only (no code changes).

Poem

🐰 In a burrow of text I neatly align,
With Summary, Changes, and Commit style fine.
Checklist checked, reviewers can play,
Clear PR paths hop the quiet way.
✨📜

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add PR template' directly and clearly summarizes the main change—adding a new pull request template file.
Description check ✅ Passed The description 'PR template to be filled out with each PR in the future' is related to the changeset and explains the purpose of the template addition.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch task/pr-template

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.

Copy link

@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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/pull_request_template.md:
- Line 27: Update the changelog checkbox link in
.github/pull_request_template.md so it no longer points to the
pgEdge/control-plane repository; replace the hardcoded URL in the line "- [ ]
[Changelog](https://github.com/pgEdge/control-plane/blob/main/docs/development/development.md#pull-requests)
entry added for user-facing behavior changes" with a generic instruction or a
relative/internal docs link (e.g., "See repository CONTRIBUTING or
docs/development for changelog entry") so contributors in pgEdge/spock are not
redirected to the control-plane repo.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 746f0d68-39da-4eb2-8045-320ba7d41c61

📥 Commits

Reviewing files that changed from the base of the PR and between 5b6732c and f1c2d4e.

📒 Files selected for processing (1)
  • .github/pull_request_template.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant