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: add CI #24

Merged
merged 19 commits into from
Sep 6, 2024
Merged

chore: add CI #24

merged 19 commits into from
Sep 6, 2024

Conversation

foxytanuki
Copy link
Member

@foxytanuki foxytanuki commented Sep 5, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a Continuous Integration (CI) workflow for automated testing and linting across Solidity, Go, and Protobuf.
    • Expanded the Makefile to support building, testing, linting, and formatting for multiple programming languages.
  • Bug Fixes

    • Implemented linting exclusions to streamline the linting process and reduce noise in results.

Copy link

coderabbitai bot commented Sep 5, 2024

Walkthrough

The changes introduce a Continuous Integration (CI) workflow for GitHub Actions, automating testing and linting for Solidity, Go, and Protobuf. The Makefile is enhanced to support various build processes, consolidating commands for multiple languages and introducing new targets for building, testing, linting, and formatting.

Changes

File(s) Change Summary
.github/workflows/ci.yaml Introduced a CI workflow for testing and linting in Solidity, Go, and Protobuf.
Makefile Expanded functionality to support multiple languages with new build, test, lint, and format targets.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant CI_Workflow
    participant Solidity
    participant Go
    participant Protobuf

    Developer->>GitHub: Push code or create pull request
    GitHub->>CI_Workflow: Trigger CI process
    CI_Workflow->>Solidity: Run tests and linting
    CI_Workflow->>Go: Run tests and linting
    CI_Workflow->>Protobuf: Compile and lint Protobuf files
    CI_Workflow->>Developer: Return results
Loading

🐇 In the meadow, I hop with glee,
New workflows bring joy, oh can't you see?
Linting and testing, all in a row,
Code quality blooms, like flowers that grow!
With Solidity, Go, and Protobuf too,
Hooray for the changes, we’re hopping anew! 🌼


Note

Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

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

@foxytanuki foxytanuki self-assigned this Sep 5, 2024
@foxytanuki foxytanuki linked an issue Sep 5, 2024 that may be closed by this pull request
Copy link
Contributor

@peaceandwhisky peaceandwhisky left a comment

Choose a reason for hiding this comment

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

LGTM!😆

@foxytanuki foxytanuki merged commit 0c7373a into main Sep 6, 2024
1 check passed
@foxytanuki foxytanuki deleted the feat/add-ci branch September 6, 2024 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add CI Pipeline
2 participants