Add PR template

[aramprice]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@aramprice has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 56 minutes and 40 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 56 minutes and 40 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e1a71b2e-b9a4-49f7-af64-49e47d00a4ee

📥 Commits

Reviewing files that changed from the base of the PR and between ddd3b47 and 421e23a.

📒 Files selected for processing (1)

• .github/pull_request_template.md

Walkthrough

A new pull request template is added that documents the contribution workflow. The template instructs contributors to follow a "Merge Forward" process: create the initial PR against the oldest applicable ubuntu branch, then sequentially create and merge PRs through merge-to-next-version branches for subsequent releases.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, making it impossible to assess relevance to the changeset.	Add a description explaining the purpose and benefits of the new PR template, such as why the Merge Forward workflow is being adopted.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding a new PR template file to the repository.
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
• Commit unit tests in branch add-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

• X
• Mastodon
• Reddit
• LinkedIn

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

[Copilot]

Pull request overview

Adds a GitHub pull request template to document the repository’s “Merge Forward” workflow, guiding contributors on how to sequence PRs across branch lines.

Changes:

• Introduces .github/pull_request_template.md describing the merge-forward process.
• Provides a step-by-step branch/PR workflow for propagating changes through subsequent branches.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

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:
- Around line 1-9: Update the pull request template to remove ambiguous
placeholders and clarify when the "Merge Forward" workflow applies: either
replace examples like <short_name_0> and <next-short_name> with a concrete
example such as `ubuntu-jammy` and `ubuntu-<next>` and add a short sentence
stating the current repo only has `ubuntu-jammy` so contributors should create
PRs into that branch now, or keep the generic placeholders but add an explicit
note that the merge-forward steps are aspirational and only apply once
additional release branches exist; refer to the placeholders <short_name_0> and
<next-short_name> so the maintainer knows exactly which tokens to change and
update the explanatory sentence describing when to follow the merge-forward
process.

🪄 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3b5f7d4d-c89a-4e11-8f8d-6180d4aad0e8

📥 Commits

Reviewing files that changed from the base of the PR and between 435d61f and ddd3b47.

📒 Files selected for processing (1)

• .github/pull_request_template.md