Skip to content

Add release branch workflow - #406

Merged
afritzler merged 1 commit into
ironcore-dev:mainfrom
afritzler:chore/release-branch
Nov 17, 2026
Merged

afritzler merged 1 commit into
ironcore-dev:mainfrom
afritzler:chore/release-branch

Conversation

@afritzler

@afritzler afritzler commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Proposed Changes

Add release branch workflow.

Summary by CodeRabbit

  • Chores
    • Release preparation is now automated for qualifying version tags, with a corresponding minor-version branch created and published.
    • This update streamlines repository maintenance. It does not add or change functionality available in the application.

Signed-off-by: Andreas Fritzler <andreas.fritzler@sap.com>
@afritzler
afritzler requested a review from a team as a code owner November 17, 2026 12:28
@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

A GitHub Actions workflow runs for version tags matching v[0-9]+.[0-9]+.0. It derives a release-<major.minor> branch name, creates the branch, and pushes it to origin.

Changes: Release branch creation

Layer / File(s) Summary
Tag-triggered branch creation
.github/workflows/create-release-branch.yml
The workflow checks out the repository with contents write permission, derives a release branch name from the tag, creates the branch, and pushes it to origin.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: hardikdr

Merge Risk: Minimal · up to b397f

This adds a workflow that creates a release branch when a version tag ending in .0 is pushed. No concrete merge-blocking risk was found.

Pre-merge checks: Passed 3 · Inconclusive 1

Failed Failed checks: 1 inconclusive

Check name Status Explanation Resolution
Description check Inconclusive The description follows the template's main heading, but it has only one bullet-style statement ("Add release branch workflow.") in place of the three template bullets. The "Fixes #" line is missing, … Expand the Proposed Changes section with the main changes as separate bullets. Include the trigger pattern (tags matching v[0-9]+.[0-9]+.0), the release-<major.minor> branch creation, and the push to origin. Add a Fixes # line with the rela…
Passed Passed checks: 3 passed

Check name Status Explanation
Title check Passed The title "Add release branch workflow" matches the main change. The PR adds a GitHub Actions workflow (create-release-branch.yml) that runs on version tag pushes, creates a release-<major.minor> bran…
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.
Full details: Title check

Explanation

The title "Add release branch workflow" matches the main change. The PR adds a GitHub Actions workflow (create-release-branch.yml) that runs on version tag pushes, creates a release-<major.minor> branch, and pushes it to origin. The title is short, specific, and describes the primary change.

Full details: Description check

Explanation

The description follows the template's main heading, but it has only one bullet-style statement ("Add release branch workflow.") in place of the three template bullets. The "Fixes #" line is missing, so no linked issue is given. The description does not explain the trigger (version tags matching v[0-9]+.[0-9]+.0), the branch naming, or the push behavior. The PR objectives reference PR #406, but the description does not cite it either.

Resolution

Expand the Proposed Changes section with the main changes as separate bullets. Include the trigger pattern (tags matching v[0-9]+.[0-9]+.0), the release-<major.minor> branch creation, and the push to origin. Add a Fixes # line with the related issue number, or state that no issue applies.

Finishing Touches

Generate unit tests (beta)

  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: fb80363e-f548-4efc-888c-3bab9728c8c6
Commits

Reviewing files that changed from the base of the PR and between 74aa866 and b397f6c.

Files selected for processing: 1

  • .github/workflows/create-release-branch.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@afritzler
afritzler merged commit e9861d5 into ironcore-dev:main Nov 17, 2026
18 checks passed
@github-project-automation github-project-automation Bot moved this to Done in Roadmap Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants