Configure GitHub CI integration

[zzaakiirr]

Summary by CodeRabbit

• Chores
  • Added GitHub Actions workflows to automatically run RSpec tests and Rubocop checks for code quality on the main branch.

[coderabbitai]

Walkthrough

The changes introduce two new GitHub Actions workflows for automated testing and code analysis in a Ruby project. One workflow runs RSpec tests on the main branch, ensuring code quality by executing unit tests. The other workflow employs Rubocop to enforce code style and quality standards on both pushes and pull requests, helping maintain consistent code formatting and detect potential issues early.

Changes

File/Path	Change Summary
.github/workflows/rspec.yml	Introduced a workflow for running RSpec tests, setting up Ruby, installing dependencies, and uploading coverage results.
.github/workflows/rubocop.yml	Added a workflow for running Rubocop on the main branch for pushes and pull requests, ensuring code style and quality.

Poem

In the garden of code we sow,
With actions set, our tests aglow. 🌟
RSpec runs, our bugs disband,
Rubocop scans, to make code grand.
A project neat, like morning dew,
With workflows smooth, and troubles few. 🐇

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 732c9ec and 5230a84.

Files selected for processing (2)

• .github/workflows/rspec.yml (1 hunks)
• .github/workflows/rubocop.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/rubocop.yml

Additional comments not posted (7)

.github/workflows/rspec.yml (7)

1-8: LGTM! Workflow name and triggers are appropriate.

The workflow is correctly named RSpec and is triggered on push to the main branch and on pull requests.

---

9-12: LGTM! Job configuration is appropriate.

The job is named rspec and runs on ubuntu-latest, which is a standard configuration.

---

13-15: LGTM! Checkout step is correctly configured.

The step uses actions/checkout@v4 to checkout the code, which is appropriate.

---

16-20: LGTM! Setup Ruby step is correctly configured.

The step uses ruby/setup-ruby@v1 to set up Ruby version 3.2 with bundler cache enabled, which is appropriate.

---

21-22: LGTM! Install dependencies step is correctly configured.

The step runs bundle install to install dependencies, which is appropriate.

---

23-26: LGTM! Run tests step is correctly configured.

The step sets the RAILS_ENV to test and runs bundle exec rspec --format documentation, which is appropriate.

---

27-32: LGTM! Upload coverage results step is correctly configured.

The step uses actions/upload-artifact@master to upload the coverage report as an artifact, which is appropriate.

[zzaakiirr]

@borela Can you take a look?

@justin808 approved usage of GitHub actions (not circleci)