Repository redirects are here

github.com

37 points·manojlds··12 comments

> There is one caveat with the new redirect support worth noting: GitHub Pages sites are not automatically redirected when their repositories are renamed at this time.

Surprising that they didn't implement this as it seems like the easiest thing to implement and pretty damn useful.

Cool. Glad it's finally here. Although I have some concerns here: Is this an option or not changeable? Does this mean you can't use [a previous name of an existing repo] as a new repo's name?

Any new repo you create will trump any redirect that has been set up.

What if I rename my account? Repository redirects are created, but would someone else be able to register with my previous username and take over repositories?

Good question.

What if you're in a situation where you have both the source and target repo already present, each with their separate issues (which you'd like to combine). I assume you'd have to combine everything in one repo, delete the other, and perform the rename. Does that sound right?

Would this affect a new repo I make if it's named after one I renamed before?

No, because it would still have a different owner, same as forks do.

He's talking about if it's by the same owner (him). See beefsack's response which answers this question.

My testing:

1. Create https://github.com/beefsack/test1

2. Rename to https://github.com/beefsack/test2, redirect works

3. Create new https://github.com/beefsack/test1, link from (1) points to this new repo

So yeah, it looks like it works.

Why this wasn't implemented at the first time. Doesn't seem hard to do...

At least with username level redirects this decreases the number of available usernames, unless this is somehow taken into account.

Reply on news.ycombinator.com