Skip to content

ci: use stable branch name for gardenlinux update workflow#1240

Merged
ideaship merged 1 commit into
mainfrom
ci/gardenlinux-stable-branch
Jun 24, 2026
Merged

ci: use stable branch name for gardenlinux update workflow#1240
ideaship merged 1 commit into
mainfrom
ci/gardenlinux-stable-branch

Conversation

@berendt

@berendt berendt commented Jun 24, 2026

Copy link
Copy Markdown
Member

Problem

The update-image-gardenlinux.yml workflow used a branch name derived from the run number (updates-image-gardenlinux-${{ github.run_number }}). Because peter-evans/create-pull-request opens one PR per unique branch, every scheduled run created a new branch and a new PR, leading to dozens of accumulated open PRs.

The equivalent update-images.yml workflow was already fixed to use a stable branch name in #1208; this brings the gardenlinux workflow in line.

Change

  • Use a fixed branch name updates-image-gardenlinux instead of one per run.
  • Fix the PR title typo mageimage.

Result

There is now exactly one branch and one PR for the gardenlinux image:

  • No merge, new change → the existing PR is updated (force-push), no new PR is opened.
  • No merge, no change → the PR stays as is.
  • After merge / no more diffs → delete-branch: true cleans up branch and PR.

🤖 Generated with Claude Code

Use a fixed branch name instead of one derived from the run number so
the gardenlinux image update produces exactly one branch and one pull
request. peter-evans/create-pull-request then updates the existing PR
on subsequent runs instead of opening a new PR every time.

Also fix the PR title typo "mage" -> "image".

Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Christian Berendt <berendt@osism.tech>
@ideaship ideaship merged commit 4244b78 into main Jun 24, 2026
3 checks passed
@ideaship ideaship deleted the ci/gardenlinux-stable-branch branch June 24, 2026 10:32
@github-project-automation github-project-automation Bot moved this from Ready to Done in Human Board Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants