Set correct branch for releases

[afritzler]

Summary by CodeRabbit

• Chores
  • Enhanced CI/CD automation to streamline release branch targeting and management processes.

[afritzler]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

A GitHub Actions workflow step is added to update the release target branch by editing the release's target_commitish to point to the newly created release branch using the gh release edit command.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/create-release-branch.yml	Adds a step to update the release target branch by setting target_commitish to the corresponding release branch (format: release-${TAG%.*}) after branch creation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Add release branching and cherry picking process #669: Modifies the same workflow to support release-branch creation; this PR adds a complementary step to update the release's target commit after the branch is created.

Suggested labels

enhancement, area/metal-automation

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided, but the template requires sections for 'Proposed Changes' and issue reference.	Add a description following the template structure, explaining what changes were made and which issue (if any) this fixes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the GitHub Actions workflow to set the correct release branch target.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-release-workflow

---

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.}