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

Merge new master branch to old fix-rubocop one #491

Open
wants to merge 191 commits into
base: fix-rubocop
Choose a base branch
from

Conversation

ShamoX
Copy link
Contributor

@ShamoX ShamoX commented Mar 8, 2019

No description provided.

gildub and others added 30 commits April 9, 2018 10:36
Replace no longer used `Style/TrailingCommaInLiteral` cop with `Style/TrailingCommaInArrayLiteral` and `Style/TrailingCommaInHashLiteral`
Remove redundant slash in get_server_volumes.rb file
Storage: Set cache-control header for a file
Signed-off-by: Melvin Hillsman <mrhillsman@gmail.com>
Signed-off-by: Melvin Hillsman <mrhillsman@gmail.com>
Depends-On: fog#392
Add playbooks directory with job definitions
Use autoload with default gem path
Replaces Openstack with OpenStack where needed
Bump ruby, fog-core versions; Each not each_pair
Rake: reduce double definition; Default launch
Jobs are failing due to timeout retrieving keys

Signed-off-by: Melvin Hillsman <mrhillsman@gmail.com>
Add additional key servers and keys
Tests: replace skip by conditional for fog-mocking
Moves autoload to allow reopening
gildub and others added 26 commits January 30, 2019 17:07
…meter

Add multiattach parameter to volume creation
Created explicit mock and real files for volume v1 and v2
Allow custom filename through Content-Disposition header
Recheck token expiration and re authenticate
@ShamoX
Copy link
Contributor Author

ShamoX commented Mar 19, 2019

OK, there is still remaining cops offended (10 remaining). But They are much touchy. I don't know when I'll be able to do then and if we can fix them.

@gildub
Copy link
Collaborator

gildub commented Mar 20, 2019

@ShamoX, that sounds good meanwhile I believe you have to start from latest commit because your PR is containing lots of already committed ones. Thanks

@ShamoX
Copy link
Contributor Author

ShamoX commented Jan 20, 2022

@gildub I'll work again on this when #521 will be merged since it also alter Rubocop behaviour in a way that seems to me with a higher priority. What do you think ?

@ShamoX
Copy link
Contributor Author

ShamoX commented Jun 30, 2022

Hello,

Should we merge this and start working on ruby 2.7 and 3.x support (as asked by #522 ) ?

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.