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

Run Rubocop as part of a different job #74

Merged
merged 2 commits into from
Feb 21, 2025
Merged

Conversation

nicolastemciuc
Copy link
Member

Summary

  • Bump rubocop constraint from 0.80.1 to ~> 1
  • Run rubocop in a different job against Ruby 3.4

Copy link
Contributor

@santiagorodriguez96 santiagorodriguez96 left a comment

Choose a reason for hiding this comment

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

Love it! Thank you! ❤️

Comment on lines +13 to +27
lint:
runs-on: ubuntu-latest

steps:
- name: Check out repository code
uses: actions/checkout@v4

- name: Set up Ruby
uses: ruby/setup-ruby@v1
with:
ruby-version: '3.4'
bundler-cache: true

- name: Lint code for consistent style
run: bundle exec rubocop -f github
Copy link
Contributor

@santiagorodriguez96 santiagorodriguez96 Feb 21, 2025

Choose a reason for hiding this comment

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

Although it's supposed that new cops are not enabled by default when introduced between major versions, I'm a little worried about the CI suddenly starting to fail as rubocop keeps releasing new versions – perhaps we could open up a separate PR to start tracking the Gemfile.lock again to ensure that we always get the same version?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes we could do that!

The Gemfile.lock only needs to support the latest Ruby version, right? We don't have to worry about EOL Ruby versions, do we?

Copy link
Contributor

Choose a reason for hiding this comment

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

Exactly!

@nicolastemciuc nicolastemciuc merged commit ab0736a into master Feb 21, 2025
47 checks passed
@santiagorodriguez96 santiagorodriguez96 deleted the nt--bump-rubocop branch February 21, 2025 14:17
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.

2 participants