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

ci: add merge_group triggers #2431

Merged
merged 3 commits into from
Jul 3, 2024
Merged

ci: add merge_group triggers #2431

merged 3 commits into from
Jul 3, 2024

Conversation

gartnera
Copy link
Member

@gartnera gartnera commented Jul 3, 2024

Description

Add merge_group triggers to all required workflows. All required status checks must be reported when using merge queue.

Run the light upgrades tests on mergequeue. This means that the upgrade tests will have to pass before merge. Update: the upgrade tests are not stable right now, let's just run default e2e for now.

Once this is approved, I will enable merge queue and this will be the first PR to merge via merge queue.

Related to #2134

How Has This Been Tested?

  • Tested CCTX in localnet
  • Tested in development environment
  • Go unit tests
  • Go integration tests
  • Tested via GitHub Actions

@gartnera gartnera requested a review from a team as a code owner July 3, 2024 19:30
Copy link
Contributor

coderabbitai bot commented Jul 3, 2024

Important

Review skipped

Review was skipped due to path filters

Files ignored due to path filters (4)
  • .github/workflows/build.yml is excluded by none and included by none
  • .github/workflows/e2e.yml is excluded by none and included by none
  • .github/workflows/generate-files.yml is excluded by none and included by none
  • .github/workflows/sast-linters.yml is excluded by none and included by none

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.

@github-actions github-actions bot added the ci Changes to CI pipeline or github actions label Jul 3, 2024
@gartnera gartnera added the no-changelog Skip changelog CI check label Jul 3, 2024
Copy link
Contributor

@CryptoFewka CryptoFewka left a comment

Choose a reason for hiding this comment

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

Looks good to me. How many jobs spin up simultaneously?

@gartnera
Copy link
Member Author

gartnera commented Jul 3, 2024

Looks good to me. How many jobs spin up simultaneously?

That is configurable in the repo settings:

image

@gartnera gartnera added this pull request to the merge queue Jul 3, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 3, 2024
@gartnera gartnera added this pull request to the merge queue Jul 3, 2024
@gartnera gartnera removed this pull request from the merge queue due to a manual request Jul 3, 2024
@gartnera gartnera enabled auto-merge July 3, 2024 20:33
@gartnera gartnera added this pull request to the merge queue Jul 3, 2024
Merged via the queue into develop with commit f45a56b Jul 3, 2024
29 of 30 checks passed
@gartnera gartnera deleted the merge-group-triggers branch July 3, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Changes to CI pipeline or github actions no-changelog Skip changelog CI check
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants