Skip to content

Do not add staging-released tag for chatbot release#3105

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
rawagner:chatbot_container
Aug 12, 2025
Merged

Do not add staging-released tag for chatbot release#3105
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
rawagner:chatbot_container

Conversation

@rawagner
Copy link
Copy Markdown
Member

@rawagner rawagner commented Aug 11, 2025

Summary by CodeRabbit

  • Chores
    • Updated release tagging rules to refine how staging tags are generated.
    • Tags ending with “-cim” or “-chatbot” are now excluded from automatic staging tag creation.
    • No changes to application features or behavior.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Aug 11, 2025

Walkthrough

The GitHub Actions workflow push-to-master.yaml updates a regex in the “Generate tags” step to exclude tags ending with -chatbot in addition to -cim when appending staging-released. No other steps or logic in the workflow are modified.

Changes

Cohort / File(s) Summary of Changes
CI Workflow
.github/workflows/push-to-master.yaml
Updated tag-generation regex from -cim$ to `-(cim

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant GH as GitHub Actions
  participant Step as Generate tags step

  Dev->>GH: Push tag
  GH->>Step: Run tag-generation logic
  alt tag ends with -cim or -chatbot
    Step-->>GH: Do not append "staging-released"
  else other tags
    Step-->>GH: Append "staging-released"
  end
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I twitch my whiskers at regex lore,
Now chatbot joins the CIM at the door.
Tags hop neatly, rules in place,
Staging carrots in the proper space.
Thump-thump! Pipelines stay on track—
A tidy warren, no suffix slack.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@openshift-ci openshift-ci bot requested review from ElayAharoni and jgyselov August 11, 2025 13:32
@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 11, 2025
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/push-to-master.yaml (1)

60-62: Consider covering pre-release variants (e.g., -chatbot-rc, -chatbot.1).

If chatbot tags sometimes include extra suffixes, the current -(cim|chatbot)$ won’t match, and staging-released would be added. If that’s undesired, broaden the regex:

-            if [[ ! "${GITHUB_REF_NAME}" =~ -(cim|chatbot)$ ]]; then
+            if [[ ! "${GITHUB_REF_NAME}" =~ -(cim|chatbot)([-.].+)?$ ]]; then

Please confirm how chatbot tags are formatted (exactly -chatbot vs. -chatbot-*). If variants exist, the above change will keep them excluded as well. I can update the PR accordingly.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 958b087 and 21abfd3.

📒 Files selected for processing (1)
  • .github/workflows/push-to-master.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: tests
  • GitHub Check: translation-files
  • GitHub Check: lint
  • GitHub Check: format
  • GitHub Check: unit-tests
  • GitHub Check: circular-deps
🔇 Additional comments (1)
.github/workflows/push-to-master.yaml (1)

60-62: Change aligns with objective — '-chatbot' no longer gets 'staging-released'.

The updated regex correctly prevents adding staging-released for tags ending with -chatbot. This matches the PR intent without altering other logic.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2025
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Aug 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82, rawagner

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rawagner
Copy link
Copy Markdown
Member Author

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 9d9bb8c into openshift-assisted:master Aug 12, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants