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

Fix Rubocop Offenses #47508

Merged
merged 1 commit into from
Mar 16, 2023
Merged

Conversation

JuanVqz
Copy link
Contributor

@JuanVqz JuanVqz commented Feb 26, 2023

Motivation / Background

This Pull Request has been created because I saw some Rubocop offenses

Detail

This Pull Request fixes some Rubocop offenses.

Additional information

Checklist

Before submitting the PR make sure the following are checked:

  • This Pull Request is related to one change. Changes that are unrelated should be opened in separate PRs.
  • Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
  • Tests are added or updated if you fix a bug or add a feature.
  • CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

@rails-bot rails-bot bot added the actionpack label Feb 26, 2023
@yahonda
Copy link
Member

yahonda commented Feb 27, 2023

Rails 6.1.Z only supports security issues as explained in the Maintenance Policy for Ruby on Rails

Let me close this pull request because addressing RuboCop offenses are not security issues.

@yahonda yahonda closed this Feb 27, 2023
@eileencodes eileencodes reopened this Mar 16, 2023
@eileencodes eileencodes merged commit a3dbc01 into rails:6-1-stable Mar 16, 2023
@eileencodes
Copy link
Member

eileencodes commented Mar 16, 2023

Merged this so we can have a green 6-1-stable for when PRs are opened to fix security releases #47667

Thank you @JuanVqz!

@JuanVqz
Copy link
Contributor Author

JuanVqz commented Mar 16, 2023

Merged this so we can have a green 6-1-stable for when PRs are opened to fix security releases #47667

Thank you @JuanVqz!

Hey @eileencodes yes, making it green was the main reason for this, now I noticed there is a new failing cop, already looked at it, it seems like we should just remove that line because is not used, could you please confirm it? then I can open a pr solving it if you agree, thanks!

The line to remove https://github.com/rails/rails/blob/6-1-stable/tasks/release.rb#L113
On the other hand in the main branch, we have this block https://github.com/rails/rails/blob/main/tasks/release.rb#L120-L130 which makes me think about how should we proceed on it.

@eileencodes
Copy link
Member

Actually I think the correct change is to backport this #45484 to 7-0-stable and 6-1-stable. Do you want to do that?

@JuanVqz
Copy link
Contributor Author

JuanVqz commented Mar 16, 2023

Actually I think the correct change is to backport this #45484 to 7-0-stable and 6-1-stable. Do you want to do that?

Sure thing! On it, thanks!

This was referenced Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants