Skip to content

[release-1.7] chore: Trigger the chart releaser workflow on both main and release branches - #193

Merged
rm3l merged 1 commit into
redhat-developer:release-1.7from
openshift-cherrypick-robot:cherry-pick-192-to-release-1.7
Jul 17, 2025
Merged

[release-1.7] chore: Trigger the chart releaser workflow on both main and release branches#193
rm3l merged 1 commit into
redhat-developer:release-1.7from
openshift-cherrypick-robot:cherry-pick-192-to-release-1.7

Conversation

@openshift-cherrypick-robot

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jul 17, 2025

Copy link
Copy Markdown

This is an automated cherry-pick of #192

/assign rm3l

Summary by Sourcery

Trigger the chart releaser workflow on both main and release branches and conditionally mark releases as latest only on main

CI:

  • Expand workflow triggers to include release-1.x branches alongside main
  • Add a conditional mark_as_latest flag to helm/chart-releaser-action for main
  • Remove extraneous blank line from cr.yaml

…ranches too

This makes it easier to test upstream releases of the chart
@sourcery-ai

sourcery-ai Bot commented Jul 17, 2025

Copy link
Copy Markdown

Reviewer's Guide

The PR enhances the chart releaser workflow by adding release-1.x branch triggers, conditionally marking main branch releases as latest, and cleans up an extra blank line in the cr.yaml configuration.

Flow diagram for conditional marking of latest chart release

flowchart TD
  A[Push to main or release-1.x branch] --> B[Trigger chart releaser workflow]
  B --> C{Is branch main?}
  C -- Yes --> D[Set mark_as_latest: true]
  C -- No --> E[Set mark_as_latest: false]
  D & E --> F[Run chart releaser action]
Loading

File-Level Changes

Change Details Files
Trigger chart releaser on release branches
  • Added regex branch filter for release-1.x under push triggers
.github/workflows/release.yaml
Conditionally mark releases as latest on main
  • Introduced mark_as_latest input using GitHub ref comparison for main branch
.github/workflows/release.yaml
Clean up cr.yaml formatting
  • Removed extraneous blank line at the end of cr.yaml
cr.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sonarqubecloud

Copy link
Copy Markdown

@rm3l rm3l left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm label Jul 17, 2025
@rm3l
rm3l merged commit 31f1e63 into redhat-developer:release-1.7 Jul 17, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants