Ransack: Rename `master` to `main`

[seanfcarroll]

See

• Guidance from ACM: https://www.acm.org/diversity-inclusion/words-matter
• Inclusive Naming Initiative: https://inclusivenaming.org/
• Google’s initiative for more inclusive language in open source projects https://opensource.googleblog.com/2020/11/googles-initiative-for-more-inclusive.html
• https://jarv.is/notes/github-rename-master/
• https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/'

[yshmarov]

This is for new repositories. Old ones don't have to be renamed

[deivid-rodriguez]

@yshmarov I know we don't _need_ to do it, but I think @seanfcarroll is bringing this up as something that we _want_ to do.

[itsalongstory]

At the technical level, a lot of libraries use master as the default branch name, renameing it to main may lead to unintended results.

gem 'ransack', github: 'activerecord-hackery/ransack'

For example, in Gemfile, this will fetch from master branch, not main branch, so I think we don't need to do it.

https://github.com/rubygems/rubygems/blob/53a1673b8edae04f0190c30506facd6b4c1e1f72/bundler/lib/bundler/source/git.rb#L25

[deivid-rodriguez]

Yes, I don't plan to change this at all unless we fix https://github.com/rubygems/rubygems/issues/4009 first and make sure that proper redirections are in place for the transition.

[seanfcarroll]

@deivid-rodriguez I see https://github.com/rubygems/rubygems/issues/4009 is closed, is it fixed now ? (wasn't clear to me in the issue).

[deivid-rodriguez]

Yes, this should be fixed now and released with bundler 2.2.5 (https://github.com/rubygems/rubygems/blob/3.2/bundler/CHANGELOG.md#225-january-11-2021). Obviously unless clients have upgraded to that version, they won't benefit from the fix.

[seanfcarroll]

Obviously unless clients have upgraded to that version, they won't benefit from the fix.

Let's give it a few more months then.