Redirect /gems/magiclink to /gems/magic-link

[bradgessler]

I recently went to publish a gem that I thought was free and available, but got this error:

$ magiclink git:(main) rake release
magiclink 0.1.0 built to pkg/magiclink-0.1.0.gem.
Tag v0.1.0 has already been created.
Pushing gem to https://rubygems.org...
There was a problem saving your gem: Name 'magiclink' is too similar to an existing gem named 'magic-link'

When I view that webpage, it looks like its fair game:

I spent 20-30 min renaming the gem from something else to magiclink. That's fine, but what pains me is to think about the number of other people that will try this for 20-30 min, push, and get rejected.

To prevent this from happening (and saving lots of dev time) I propose that urls like https://rubygems.org/gems/magiclink get redirects to https://rubygems.org/gems/magic-link or some message is displayed informing the dev that they can't have that gem name.

[simi]

Sounds good, we do already render something special for blacklisted gems here.

rubygems.org/app/controllers/rubygems_controller.rb

Lines 22 to 25 in 47ddef4

	def show
	if @blacklisted_gem
	render "blacklisted"
	else

Gem typo is checked here in pusher.

rubygems.org/app/models/rubygem.rb

Lines 372 to 377 in 47ddef4

	def protected_gem_typo
	gem_typo = GemTypo.new(name)
	return unless gem_typo.protected_typo?
	errors.add :name, "'#{name}' is too similar to an existing gem named '#{gem_typo.protected_gem}'"
	end

It should be possible to update GemTypo model to return which already existing Rubygem is in conflict and redirect in there with flash message explaining what has happened.

Would you mind to contribute?

[bradgessler]

Sure! I'll give it a go if you're the person who would be able to review and merge the PR if the implementation looks good. I don't want to spend time hacking on it and have another reviewer reject it on principal.

[simi]

Yup, I can help you to get merged this. Ping me at PR description.