ruby.git/lib/bundler/templates/newgem/rubocop.yml.tt, branch ruby_3_4

[rubygems/rubygems] Remove redundant rubocop configs

2024-02-19T04:48:42+00:00

https://github.com/rubygems/rubygems/commit/a3f60240bf

[rubygems/rubygems] Partly reverted

2023-03-28T07:26:46+00:00

https://github.com/rubygems/rubygems/pull/6541

https://github.com/rubygems/rubygems/commit/21e07a04a1

[rubygems/rubygems] Generate native gems with `-fvisibility=hidden`

2023-03-25T00:31:46+00:00

I recently ran into very nasty issues with dynamic symbols clashing between
two native gems.

I believe the overwhelming majority of native gems don't want to export
their symbols, so hidding them by default would make sense to me.

https://github.com/rubygems/rubygems/commit/449624aa54

Sync latest development version of bundler & rubygems

2021-03-08T04:47:35+00:00

[rubygems/rubygems] Lock rubocop version to 0.80.1

2020-07-15T07:05:12+00:00

The later RuboCop versions don't work with ruby2.3
so we should lock the version to what works with
ruby2.3 as we haven't dropped the support yet.

And since we're using the older version of rubocop,
also fix `Max` value of `LineLength` to 120, which
is the current standard. Without this, rubocop
will throw the line length offenses.

Signed-off-by: Utkarsh Gupta 

https://github.com/rubygems/rubygems/commit/46d0a800a2

Ship default .rubocop.yml

2020-06-18T10:14:15+00:00

Currently, there is no `.rubocop.yml` shipped by default.
So when a user runs `rubocop` after creating a new gem via
`bundle gem foo`, it throws a bunch of offenses.

With the default `.rubocop.yml` present, the number of those
offenses significantly reduce by 25.

Signed-off-by: Utkarsh Gupta