Skip to content

[ci] Do not run tests in release building pipeline - #882

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
fix-test-tags
Apr 24, 2025
Merged

[ci] Do not run tests in release building pipeline#882
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
fix-test-tags

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented Apr 24, 2025

Copy link
Copy Markdown
Member

Signed-off-by: Andrei Kvapil kvapss@gmail.com

Summary by CodeRabbit

  • Chores
    • Removed the "Test" step from the release workflow, so tests will no longer run as part of this process.

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai

coderabbitai Bot commented Apr 24, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The "Test" step, responsible for conditionally running make test, has been removed from the .github/workflows/tags.yaml GitHub Actions workflow. No other steps or logic within the workflow file were changed, and there were no alterations to public or exported entities in the codebase.

Changes

File(s) Change Summary
.github/workflows/tags.yaml Removed the "Test" workflow step that ran make test conditionally. No other changes made.

Suggested reviewers

  • klinch0
  • lllamnyp

Poem

A workflow once hopped with a test in its track,
But now that step’s gone—no more looking back!
The tags flow more swiftly, the path is now clear,
No tests to delay us, the finish is near.
With a twitch of my nose and a hop in my code,
Onward we go, down a lighter workflow road! 🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7be5db8 and 7db7277.

📒 Files selected for processing (1)
  • .github/workflows/tags.yaml (0 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/tags.yaml

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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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

@NickVolynkin Nick Volynkin (NickVolynkin) added the backport Should change be backported on previous release label Apr 24, 2025
@kvaps
Andrei Kvapil (kvaps) merged commit 455d66f into main Apr 24, 2025
@kvaps
Andrei Kvapil (kvaps) deleted the fix-test-tags branch April 24, 2025 13:27
@github-actions

Copy link
Copy Markdown

Git push to origin failed for release-0.30 with exitcode 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Should change be backported on previous release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants