Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: push docker dev images on iavl-v1 #7995

Merged
merged 1 commit into from
Apr 9, 2024
Merged

chore: push docker dev images on iavl-v1 #7995

merged 1 commit into from
Apr 9, 2024

Conversation

p0mvn
Copy link
Member

@p0mvn p0mvn commented Apr 9, 2024

Closes: #XXX

What is the purpose of the change

Currently, we do no auto-push docker dev images. This PR attempts to fix this

@p0mvn p0mvn added V:state/compatible/backport State machine compatible PR, should be backported A:backport/v23.x backport patches to v23.x branch labels Apr 9, 2024
@github-actions github-actions bot added the T:CI label Apr 9, 2024
@p0mvn p0mvn marked this pull request as ready for review April 9, 2024 04:44
@p0mvn p0mvn requested a review from a team as a code owner April 9, 2024 04:44
Copy link
Contributor

coderabbitai bot commented Apr 9, 2024

Walkthrough

A recent update has expanded the conditions under which a specific workflow is triggered. This enhancement involves adding a new branch pattern to the existing workflow configurations, ensuring that the workflow is also activated for branches named according to a new convention, alongside the already supported main and version-specific branches. This adjustment broadens the workflow's applicability, facilitating its execution across a wider array of development branches.

Changes

File Summary of Changes
.github/workflows/push-dev-docker-images.yml Added branch pattern v[0-9]+.x-iavl-v1 to trigger workflow.

🐇✨
In the realm of code, where branches intertwine,
A new path emerges, as stars align.
v[0-9]+.x-iavl-v1, a pattern so fine,
Triggers workflows with magic, by design.
So hop along, devs, with joy in your heart,
For every commit, a new journey starts.
🚀🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Copy link
Member

@czarcas7ic czarcas7ic left a comment

Choose a reason for hiding this comment

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

utACK

@p0mvn p0mvn merged commit 90f159d into main Apr 9, 2024
1 check passed
@p0mvn p0mvn deleted the roman/dev-images branch April 9, 2024 08:07
mergify bot pushed a commit that referenced this pull request Apr 9, 2024
mergify bot pushed a commit that referenced this pull request Apr 9, 2024
czarcas7ic pushed a commit that referenced this pull request Apr 9, 2024
(cherry picked from commit 90f159d)

Co-authored-by: Roman <roman@osmosis.team>
czarcas7ic pushed a commit that referenced this pull request Apr 9, 2024
(cherry picked from commit 90f159d)

Co-authored-by: Roman <roman@osmosis.team>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A:backport/v23.x backport patches to v23.x branch T:CI V:state/compatible/backport State machine compatible PR, should be backported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants