Skip to content

Update PR template#629

Merged
aramprice merged 1 commit into
ubuntu-jammyfrom
update-pr-template
Jun 10, 2026
Merged

Update PR template#629
aramprice merged 1 commit into
ubuntu-jammyfrom
update-pr-template

Conversation

@aramprice

Copy link
Copy Markdown
Member

NOTE: this repository uses a "Merge Forward" strategy

Changes should be made in the earliest applicable branch, and
merged forward through subsequent branches.

  1. Create a PR into the oldest branch (ubuntu-<short_name>)
  2. After this PR has been merged create a merge-to-<next_short_name> branch
  3. Merge ubuntu-<short_name> into merge-to-<next_short_name>
  4. Create a PR to merge merge-to-<next_short_name> into ubuntu-<next_short_name>
  5. Repeat as needed for subsequent branches

Copilot AI review requested due to automatic review settings June 10, 2026 03:43

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s pull request template instructions for the “merge forward” workflow, aiming to simplify how changes are propagated across supported Ubuntu stemcell line branches.

Changes:

  • Replaces the previous multi-step “merge-to-*” branch instructions with a simpler “PR merges from oldest branch to next branch” flow.
  • Updates the example branch naming used in the merge-forward instructions.

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

Comment thread .github/pull_request_template.md
@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The pull request updates .github/pull_request_template.md to document a new "merge forward" workflow for branching operations. The instructions now reflect that PRs should be created against the oldest stemcell branch (e.g., ubuntu-<short_name-N>), and after merge, subsequent PRs should merge that branch into the next sequential branch (ubuntu-<short_name-N+1>), repeating as needed. The previous workflow describing merge-to-<next_short_name> intermediary branches has been removed.

Suggested reviewers

  • mariash
  • mkocher
  • selzoc
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Update PR template' is vague and generic, using non-descriptive language that doesn't convey meaningful information about what specifically changed in the template. Consider a more specific title like 'Update PR template with Merge Forward strategy' or 'Simplify PR template with streamlined merge process'.
✅ Passed checks (4 passed)
Check name Status Explanation
Description check ✅ Passed The PR description matches the repository template structure and includes all required sections with the Merge Forward strategy clearly outlined in a step-by-step format.
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 update-pr-template

Warning

Review ran into problems

🔥 Problems

Stopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a @coderabbit review after the pipeline has finished.


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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/pull_request_template.md:
- Around line 5-6: Update the PR template text that currently uses the
placeholders "ubuntu-<short_name-N>" and "ubuntu-<short_name-N+1>" to include
concrete examples for clarity (e.g., "ubuntu-focal-1" -> "ubuntu-focal-2" or
"ubuntu-20.04-1" -> "ubuntu-20.04-2"); modify the two lines containing those
placeholders so they show both the placeholder and one or two explicit example
branch names to illustrate the intended workflow and reduce ambiguity for
contributors.
🪄 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: 56fb16cd-b124-4af0-bc69-08d1b3b3c77c

📥 Commits

Reviewing files that changed from the base of the PR and between dfe1504 and 9223f9d.

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

Comment thread .github/pull_request_template.md
@aramprice aramprice merged commit b5a0b15 into ubuntu-jammy Jun 10, 2026
13 checks passed
@aramprice aramprice deleted the update-pr-template branch June 10, 2026 03:48
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.

2 participants