fix(config/pull-request-template): update broken link

[JeremyFriesenGitHub]

Checklist

• I've thoroughly read the latest contribution guidelines.
• I've rebased my branch onto main before creating this PR.
• I've added tests to cover my changes (if applicable).
• I've verified that all new and existing tests have passed locally for mobile, tablet, and desktop screen sizes.
• My commit messages follow guidelines
• My change requires documentation updates.
• I've updated the documentation accordingly.
• My code follows existing patterns of this project and/or improves upon them.

---

Summary by CodeRabbit

• Documentation
  • Updated pull request template with a modified link reference for commit message guidelines.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request modifies the GitHub pull request template by updating a link reference in the checklist section. Specifically, the text "guidelines" has been changed to "concepts" in the line about commit message guidelines. This suggests a potential update to the documentation structure or URL routing for commit message guidelines.

Changes

File	Change Summary
.github/pull_request_template.md	Updated link reference from "guidelines" to "concepts" in commit message guidelines section

Possibly related issues

• cuhacking/2025#244: This issue directly relates to fixing a broken link in the pull request template, which matches the changes in this PR. The issue describes a 404 page when trying to access guidelines, which this PR appears to be addressing.

Possibly related PRs

• docs(contribution-guidelines): add github issue and pull request guidelines and templates #83: Enhances contribution guidelines and templates
• docs(getting-started): fix typo #203: Fixes documentation typo in getting started section

Suggested labels

bug

Suggested reviewers

• MFarabi619

Poem

🐰 A rabbit's tale of links so bright,
Where "guidelines" shifts to "concepts" light
A template tweak, a URL's dance
Fixing paths with coding's glance
Hop along, pull request so neat! 🔗

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2a18268 and d223be6.

📒 Files selected for processing (1)

• .github/pull_request_template.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/pull_request_template.md

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.