Ros2 devel pr template

[delihus]

Description

Added checkbox to update submodules.

Requirements

• Code style guidelines followed
• Documentation updated

Tests 🧪

• Robot
• Container
• Simulation

Summary by CodeRabbit

• New Features
  • Enhanced pull request template with new checkboxes for indicating dependency pull requests and confirming updates to other repositories.

These updates improve clarity and ensure completeness when submitting pull requests.

[coderabbitai]

Walkthrough

The changes involve modifications to the pull request template located in .github/pull_request_template.md. Two new checkbox items have been added to the "Requirements" section: one for indicating a dependency pull request and another to confirm that other repositories have been updated in the .repos file. The "Tests" section remains unchanged.

Changes

File	Change Summary
.github/pull_request_template.md	Added checkbox for (Dependency PR) and Other repositories updated .repos in "Requirements".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant PR_Template

    User->>PR_Template: Fill out pull request
    PR_Template->>User: Display requirements
    User->>PR_Template: Check `(Dependency PR)`
    User->>PR_Template: Check `Other repositories updated .repos`
    User->>PR_Template: Submit pull request

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

.github/pull_request_template.md (2)

7-10: Enhance clarity of the new checkboxes

The new checkboxes are valuable additions but could benefit from more context to guide contributors effectively.

Consider this improved wording:

-- [ ] (Dependency PR)
-- [ ] Other repositories updated `.repos`
+- [ ] Dependency PR (if applicable): Link to related PR in other repositories
+- [ ] Updated `.repos` file with new repository versions (if dependencies changed)

This change would:

1. Clarify when the Dependency PR checkbox is relevant
2. Provide explicit guidance about the .repos file updates
3. Help maintainers better track cross-repository changes

---

7-10: Consider additional ROS2-specific checkboxes

Since this is a ROS2 project, consider adding these checkboxes to ensure comprehensive verification:

 - [ ] (Dependency PR)
 - [ ] Code style guidelines followed
 - [ ] Documentation updated
 - [ ] Other repositories updated `.repos`
+- [ ] Verified compatibility with ROS2 $DISTRO (e.g., humble, iron)
+- [ ] Tested workspace builds cleanly with colcon

This would help ensure:

1. ROS2 distribution compatibility is explicitly checked
2. Workspace build issues are caught early

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4fc2d95 and 2fd0b8c.

📒 Files selected for processing (1)

• .github/pull_request_template.md (1 hunks)

🔇 Additional comments (1)

.github/pull_request_template.md (1)

Line range hint 1-15: Template structure and changes look good!

The additions to the Requirements section effectively support the goal of improving submodule management while maintaining a clear and organized template structure. The existing sections (Description, Requirements, Tests) provide good coverage of the necessary checks for contributions.