feat: add pull request templates for bug fixes, features, and integrations#1044
Merged
Crunchyman-ralph merged 6 commits intonextfrom Jul 24, 2025
Merged
Conversation
…tions - Introduced a comprehensive pull request template structure to streamline contributions. - Added specific templates for bug fixes, new features, and integrations to enhance clarity and consistency in PR submissions. - Configured the pull request template settings for better user guidance during the contribution process.
|
Contributor
|
Warning Rate limit exceeded@Crunchyman-ralph has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 46 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughSeveral new pull request template markdown files and a configuration file were added under the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes ✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🔭 Outside diff range comments (2)
.github/PULL_REQUEST_TEMPLATE/bugfix.md (1)
1-40: Apply markdown-lint spacing to avoid CI noiseAs with the integration template, consecutive headings / lists violate MD022/MD032 and MD041 (missing H1). Add blank lines after each heading and before/after fenced blocks.
-## 🐛 Bug Fix +# 🐛 Bug Fix + ### 🔍 Bug Description + <!-- Describe the bug --> + ### 🔗 Related Issues + <!-- Fixes #123 --> + ### ✨ Solution + <!-- How does this PR fix the bug? --> + ## How to Test + ### Steps that caused the bug: + 1. 2.Updating the rest of the file accordingly will keep markdown-lint green.
.github/PULL_REQUEST_TEMPLATE/feature.md (1)
1-50: Consistent heading hierarchy & blank-line spacing neededSame lint breaks here: first line should be H1, headings require surrounding blank lines, fenced code blocks need padding.
-## ✨ New Feature +# ✨ New Feature + ### 📋 Feature Description + <!-- Brief description --> + ### 🎯 Problem Statement + <!-- What problem does this feature solve? Why is it needed? --> + ### 💡 Solution + <!-- How does this feature solve the problem? What's the approach? --> + ### 🔗 Related Issues + <!-- Link related issues: Fixes #123, Part of #456 --> + ## How to Use It + ### Quick Start + ```bash # Basic usage examplePropagate the pattern through the remainder of the template. </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: .coderabbit.yaml** **Review profile: ASSERTIVE** **Plan: Pro** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 31b8407dbc16a6c1f61a2910314ca1b5c31b1163 and 86315279a80e65b1b0fe703534efadb973ab257a. </details> <details> <summary>📒 Files selected for processing (6)</summary> * `.github/PULL_REQUEST_TEMPLATE.md` (1 hunks) * `.github/PULL_REQUEST_TEMPLATE/bugfix.md` (1 hunks) * `.github/PULL_REQUEST_TEMPLATE/config.yml` (1 hunks) * `.github/PULL_REQUEST_TEMPLATE/feature.md` (1 hunks) * `.github/PULL_REQUEST_TEMPLATE/integration.md` (1 hunks) * `package.json` (1 hunks) </details> <details> <summary>🧰 Additional context used</summary> <details> <summary>🧠 Learnings (2)</summary> <details> <summary>📓 Common learnings</summary>Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.773Z
Learning: Pull Request descriptions must use the provided template, including Task Overview, Subtasks Completed, Implementation Details, Testing, Breaking Changes, and Related TasksLearnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Every pull request containing new features, bug fixes, breaking changes, performance improvements, significant refactoring, user-facing documentation updates, dependency updates, or impactful build/tooling changes should include a changeset file.Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.773Z
Learning: Pull Request titles must follow the format: Task :Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.647Z
Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc).Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.773Z
Learning: Use commit type prefixes: feat(task-X):, fix(task-X):, test(task-X):, docs(task-X):, refactor(task-X):, chore(task-X): for all commits</details> <details> <summary>.github/PULL_REQUEST_TEMPLATE/integration.md (10)</summary> Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/glossary.mdc:0-0 Timestamp: 2025-07-18T17:10:53.647Z Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc). Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/glossary.mdc:0-0 Timestamp: 2025-07-18T17:10:53.647Z Learning: Guide for using Task Master to manage task-driven development workflows with tagged task lists support (dev_workflow.mdc). Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/glossary.mdc:0-0 Timestamp: 2025-07-18T17:10:53.647Z Learning: Guidelines for implementing and maintaining tests for Task Master CLI (tests.mdc). Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: assets/.windsurfrules:0-0 Timestamp: 2025-07-18T17:19:27.346Z Learning: Use `task-master add-task` to add a new task to tasks.json using AI. Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/new_features.mdc:0-0 Timestamp: 2025-07-18T17:12:57.858Z Learning: Applies to scripts/modules/**/*.test.js : Test CLI and MCP interfaces with real task data, verify end-to-end workflows across tag contexts, and test error scenarios and recovery in integration tests. Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: assets/.windsurfrules:0-0 Timestamp: 2025-07-18T17:19:27.346Z Learning: View specific task details using `task-master show <id>` to understand implementation requirements. Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/glossary.mdc:0-0 Timestamp: 2025-07-18T17:10:53.647Z Learning: Describes the high-level architecture of the Task Master CLI application, including the new tagged task lists system (architecture.mdc). Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/glossary.mdc:0-0 Timestamp: 2025-07-18T17:10:53.647Z Learning: Guidelines for integrating AI usage telemetry across Task Master (telemetry.mdc). Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/tasks.mdc:0-0 Timestamp: 2025-07-18T17:14:29.373Z Learning: Applies to scripts/modules/task-manager.js : Use consistent formatting for task files, include all task properties in text files, and format dependencies with status indicators. Learnt from: CR PR: eyaltoledano/claude-task-master#0 File: .cursor/rules/dev_workflow.mdc:0-0 Timestamp: 2025-07-18T17:10:12.852Z Learning: Use the Taskmaster command set (`task-master` CLI or MCP tools) for all task management operations: listing, expanding, updating, tagging, and status changes. </details> </details><details> <summary>🪛 YAMLlint (1.37.1)</summary> <details> <summary>.github/PULL_REQUEST_TEMPLATE/config.yml</summary> [error] 11-11: no new line character at the end of file (new-line-at-end-of-file) </details> </details> <details> <summary>🪛 LanguageTool</summary> <details> <summary>.github/PULL_REQUEST_TEMPLATE/integration.md</summary> [grammar] ~1-~1: Use correct spacing Context: ## 🔌 New Integration ### What tool/IDE is being integrated? <!-- ... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~3-~3: Use correct spacing Context: ...Integration ### What tool/IDE is being integrated? <!-- Name and brief description --> ### What can users do with it? <!-- Key bene... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~6-~6: Use correct spacing Context: ...ription --> ### What can users do with it? <!-- Key benefits --> ## How to Enable ### Setup ```bash task-ma... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~9-~9: Use correct spacing Context: ...th it? <!-- Key benefits --> ## How to Enable ### Setup ```bash task-master rules add [nam... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~17-~17: Use correct spacing Context: ... Any other setup steps ``` ### Example Usage <!-- Show it in action --> ```bash # Real example ``` ### Natural Language Hooks (if applicable) `... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~23-~23: Use correct spacing Context: ...ple ``` ### Natural Language Hooks (if applicable) ``` "When tests pass, mark task as done" # Other examples ``` ## Contributor Checklist - [ ] Created chan... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~38-~38: Use correct spacing Context: ...up guide - [ ] Examples are working and clear --- ### For Maintainers - [ ] Integration stabi... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~42-~42: Use correct spacing Context: ...les are working and clear --- ### For Maintainers - [ ] Integration stability verified - [ ]... (QB_NEW_EN_OTHER_ERROR_IDS_5) </details> <details> <summary>.github/PULL_REQUEST_TEMPLATE/feature.md</summary> [grammar] ~1-~1: Use correct spacing Context: ## ✨ New Feature ### 📋 Feature Description <!-- Brief descri... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~3-~3: Use correct spacing Context: ## ✨ New Feature ### 📋 Feature Description <!-- Brief description --> ### 🎯 Problem Statement <!-- What problem d... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~6-~6: Use correct spacing Context: ...- Brief description --> ### 🎯 Problem Statement <!-- What problem does this feature solve? Why is it needed? --> ### 💡 Solution <!-- How does this feature s... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~9-~9: Use correct spacing Context: ...re solve? Why is it needed? --> ### 💡 Solution <!-- How does this feature solve the problem? What's the approach? --> ### 🔗 Related Issues <!-- Link related issu... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~12-~12: Use correct spacing Context: ...hat's the approach? --> ### 🔗 Related Issues <!-- Link related issues: Fixes #123, Part of #456 --> ## How to Use It ### Quick Start ```bash #... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~15-~15: Use correct spacing Context: ...s #123, Part of #456 --> ## How to Use It ### Quick Start ```bash # Basic usage exampl... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~17-~17: Use correct spacing Context: ...f #456 --> ## How to Use It ### Quick Start ```bash # Basic usage example ``` ### Example <!-- Show a real use case --> ``... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~28-~28: Use correct spacing Context: ...ractical example ``` **What you should see:** <!-- Expected behavior --> ## Contributor Checklist - [ ] Created chan... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~38-~38: Use correct spacing Context: ...e - [ ] Manually tested in MCP mode (if applicable) ## Changelog Entry <!-- One-liner for relea... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~40-~40: Use correct spacing Context: ... MCP mode (if applicable) ## Changelog Entry <!-- One-liner for release notes --> --- ### For Maintainers - [ ] Feature aligns wi... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~45-~45: Use correct spacing Context: ...ner for release notes --> --- ### For Maintainers - [ ] Feature aligns with project vision -... (QB_NEW_EN_OTHER_ERROR_IDS_5) </details> <details> <summary>.github/PULL_REQUEST_TEMPLATE/bugfix.md</summary> [grammar] ~1-~1: Use correct spacing Context: ## 🐛 Bug Fix ### 🔍 Bug Description <!-- Describe the bug... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~3-~3: Use correct spacing Context: ## 🐛 Bug Fix ### 🔍 Bug Description <!-- Describe the bug --> ### 🔗 Related Issues <!-- Fixes #123 --> #... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~6-~6: Use correct spacing Context: ...-- Describe the bug --> ### 🔗 Related Issues <!-- Fixes #123 --> ### ✨ Solution <!-- How does this PR fix the... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~9-~9: Use correct spacing Context: ...lated Issues <!-- Fixes #123 --> ### ✨ Solution <!-- How does this PR fix the bug? --> ## How to Test ### Steps that caused the b... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~12-~12: Use correct spacing Context: ...oes this PR fix the bug? --> ## How to Test ### Steps that caused the bug: 1. 2. **Be... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~14-~14: Use correct spacing Context: ... How to Test ### Steps that caused the bug: 1. 2. **Before fix:** **After fix:** ### Quic... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~19-~19: Use correct spacing Context: ... bug: 1. 2. **Before fix:** **After fix:** ### Quick verification: ```bash # Commands t... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~21-~21: Use correct spacing Context: ...fore fix:** **After fix:** ### Quick verification: ```bash # Commands to verify the fix ``` ## Contributor Checklist - [ ] Created chan... (QB_NEW_EN_OTHER_ERROR_IDS_5) --- [grammar] ~32-~32: Use correct spacing Context: ...icable) - [ ] Manually verified the fix works --- ### For Maintainers - [ ] Root cause identif... (QB_NEW_EN_OTHER_ERROR_IDS_5) </details> </details> <details> <summary>🪛 markdownlint-cli2 (0.17.2)</summary> <details> <summary>.github/PULL_REQUEST_TEMPLATE/integration.md</summary> 1-1: First line in a file should be a top-level heading (MD041, first-line-heading, first-line-h1) --- 14-14: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 14-14: Trailing punctuation in heading Punctuation: ':' (MD026, no-trailing-punctuation) --- 15-15: Trailing spaces Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) --- 15-15: Lists should be surrounded by blank lines (MD032, blanks-around-lists) --- 16-16: Trailing spaces Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) --- 18-18: Trailing spaces Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) --- 19-19: Trailing spaces Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) --- 21-21: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 21-21: Trailing punctuation in heading Punctuation: ':' (MD026, no-trailing-punctuation) --- 22-22: Fenced code blocks should be surrounded by blank lines (MD031, blanks-around-fences) --- 26-26: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 27-27: Lists should be surrounded by blank lines (MD032, blanks-around-lists) --- 36-36: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 37-37: Lists should be surrounded by blank lines (MD032, blanks-around-lists) --- 39-39: Files should end with a single newline character (MD047, single-trailing-newline) </details> <details> <summary>.github/PULL_REQUEST_TEMPLATE/feature.md</summary> 1-1: First line in a file should be a top-level heading (MD041, first-line-heading, first-line-h1) --- 17-17: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 18-18: Fenced code blocks should be surrounded by blank lines (MD031, blanks-around-fences) --- 31-31: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 32-32: Lists should be surrounded by blank lines (MD032, blanks-around-lists) </details> <details> <summary>.github/PULL_REQUEST_TEMPLATE.md</summary> 1-1: First line in a file should be a top-level heading (MD041, first-line-heading, first-line-h1) --- 8-8: Trailing spaces Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) --- 25-25: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 26-26: Lists should be surrounded by blank lines (MD032, blanks-around-lists) --- 39-39: Headings should be surrounded by blank lines Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) --- 40-40: Lists should be surrounded by blank lines (MD032, blanks-around-lists) --- 43-43: Files should end with a single newline character (MD047, single-trailing-newline) </details> </details> </details> <details> <summary>🔇 Additional comments (1)</summary><blockquote> <details> <summary>package.json (1)</summary> `12-12`: **Formatting change is harmless – approved** The line-array → single-line change does not impact behaviour and keeps JSON valid. No further action required. </details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
Comment on lines
+10
to
+24
| ## Description | ||
| <!-- What does this PR do? --> | ||
|
|
||
| ## Related Issues | ||
| <!-- Link issues: Fixes #123 --> | ||
|
|
||
| ## How to Test This | ||
| <!-- Quick steps to verify the changes work --> | ||
| ```bash | ||
| # Example commands or steps | ||
| ``` | ||
|
|
||
| **Expected result:** | ||
| <!-- What should happen? --> | ||
|
|
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add sections required by internal contribution guidelines
Our documented workflow (see .cursor/rules/git_workflow.mdc) expects PRs to contain:
• Task Overview / Implementation Details
• Sub-tasks completed
• Breaking Changes & Related Tasks
Consider expanding the template here to keep every PR uniformly descriptive and reduce back-and-forth with reviewers.
Example insertion after “Description”:
## Implementation Details
<!-- Technical notes, libraries touched, rationale -->
## Breaking Changes
<!-- API removals, behavioural shifts, migration notes -->
## Sub-tasks Completed
<!-- Bullet list of finished work items -->🤖 Prompt for AI Agents
In .github/PULL_REQUEST_TEMPLATE.md around lines 10 to 24, the PR template lacks
sections required by internal contribution guidelines. Add new sections after
"Description" titled "Implementation Details," "Breaking Changes," and
"Sub-tasks Completed" with appropriate placeholders for technical notes, API
changes, and completed work items to ensure uniform and comprehensive PR
descriptions.
Comment on lines
+1
to
+11
| blank_issues_enabled: false | ||
| contact_links: | ||
| - name: 🐛 Bug Fix | ||
| url: https://github.com/eyaltoledano/claude-task-master/compare/next...HEAD?template=bugfix.md | ||
| about: Fix a bug in Task Master | ||
| - name: ✨ New Feature | ||
| url: https://github.com/eyaltoledano/claude-task-master/compare/next...HEAD?template=feature.md | ||
| about: Add a new feature to Task Master | ||
| - name: 🔌 New Integration | ||
| url: https://github.com/eyaltoledano/claude-task-master/compare/next...HEAD?template=integration.md | ||
| about: Add support for a new tool, IDE, or platform No newline at end of file |
Contributor
There was a problem hiding this comment.
🧹 Nitpick (assertive)
Terminate file with a newline
YAML-lint flags the missing trailing newline (MD047 / new-line-at-end-of-file).
Add a single “\n” after line 11.
about: Add support for a new tool, IDE, or platform
+ ## EOF newlineCommittable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 YAMLlint (1.37.1)
[error] 11-11: no new line character at the end of file
(new-line-at-end-of-file)
🤖 Prompt for AI Agents
In .github/PULL_REQUEST_TEMPLATE/config.yml at the end of line 11, add a single
newline character to ensure the file ends with a newline. This will fix the
YAML-lint warning about the missing trailing newline.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Collaborator
Author
|
@CodeRabbit review |
Contributor
✅ Actions performedReview triggered.
|
2 similar comments
Contributor
✅ Actions performedReview triggered.
|
Contributor
✅ Actions performedReview triggered.
|
Collaborator
Author
|
@CodeRabbit review one last time |
Contributor
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain@Crunchyman-ralph, I'll conduct a thorough review of your pull request templates. Let me analyze the structure and content of each template. 🏁 Script executed: Length of output: 5026 Excellent work on these PR templates! I've reviewed all the templates and they're very comprehensive. Here's my analysis: ✅ StrengthsStructure & Consistency:
Comprehensive Coverage:
Practical Elements:
🔧 Minor Suggestions
🎯 Overall AssessmentThis is a well-thought-out template system that will significantly improve PR quality and consistency. The templates strike a good balance between being comprehensive and not overwhelming contributors. Recommendation: ✅ Approve - These templates are ready for production use and will greatly benefit your project's contribution process. The changeset-bot reminder is actually helpful here - you'll want to add one since this is a feature addition that improves the developer experience. 🐰 These templates look great! I'm excited to see how they'll streamline your contribution process. |
Crunchyman-ralph
added a commit
to DavidMaliglowka/claude-task-master
that referenced
this pull request
Jul 28, 2025
…tions (eyaltoledano#1044) * feat: add pull request templates for bug fixes, features, and integrations - Introduced a comprehensive pull request template structure to streamline contributions. - Added specific templates for bug fixes, new features, and integrations to enhance clarity and consistency in PR submissions. - Configured the pull request template settings for better user guidance during the contribution process. * chore: fix format * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * chore: implement PR requested changes --------- Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
7 tasks
stephanschielke
pushed a commit
to stephanschielke/cursor-task-master
that referenced
this pull request
Aug 22, 2025
…tions (eyaltoledano#1044) * feat: add pull request templates for bug fixes, features, and integrations - Introduced a comprehensive pull request template structure to streamline contributions. - Added specific templates for bug fixes, new features, and integrations to enhance clarity and consistency in PR submissions. - Configured the pull request template settings for better user guidance during the contribution process. * chore: fix format * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * chore: implement PR requested changes --------- Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
stephanschielke
pushed a commit
to stephanschielke/cursor-task-master
that referenced
this pull request
Aug 22, 2025
…tions (eyaltoledano#1044) * feat: add pull request templates for bug fixes, features, and integrations - Introduced a comprehensive pull request template structure to streamline contributions. - Added specific templates for bug fixes, new features, and integrations to enhance clarity and consistency in PR submissions. - Configured the pull request template settings for better user guidance during the contribution process. * chore: fix format * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * chore: implement PR requested changes --------- Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
sfc-gh-dflippo
pushed a commit
to sfc-gh-dflippo/task-master-ai
that referenced
this pull request
Dec 4, 2025
…tions (eyaltoledano#1044) * feat: add pull request templates for bug fixes, features, and integrations - Introduced a comprehensive pull request template structure to streamline contributions. - Added specific templates for bug fixes, new features, and integrations to enhance clarity and consistency in PR submissions. - Configured the pull request template settings for better user guidance during the contribution process. * chore: fix format * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * chore: implement PR requested changes --------- Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
Documentation
Style