Twitter Bootstrap was moved from the Twitter organization to the TWBS organization. This has resulted in numerous broken links all over the Internet, and it would be nice if GitHub did something about it.

Nevertheless, Stack Overflow has a large number of links to issues on the Bootstrap project which are now broken (see this edit: https://stackoverflow.com/posts/9760366/revisions).

Could we look into replacing all github.com/twitter/bootstrap/ with github.com/twbs/bootstrap/?

Or less agressively github.com/twitter/bootstrap/issues/ with github.com/twbs/bootstrap/issues/?

  • You're calling out GitHub on a Meta SO post. Did GitHub Support already come back to you on what their end of the deal is? – random Oct 1 '13 at 2:33
  • I probably could have done more investigation, but I've seen this behavior for quite a while (maybe months?), so from pure observation it seems that they aren't taking care of it, but I could be wrong. I would assume with such an obviously impactful move (bootstrap being so popular) that they would have taken care of this. Put short, I'm assuming a bit and taking the 'short route' to fix the problem on SO – TJB Oct 1 '13 at 3:46

As of 2013-10-02, the redirects for issues and pull requests in the old Bootstrap repository appear to be functioning, so no edits are necessary.

Generally, there's supposed to be a redirect from the old GitHub repository to the new one in cases like this. This wasn't working after Bootstrap's transition to its new organisation, so someone opened a relevant issue.

Since it was marked closed, I assume that they got things sorted out at the time, but as it's broken now I've gone ahead and asked if the current behaviour is expected. If it isn't and the redirect can be (re)fixed, then there's no need to edit anything as the links should just start working again once the problem is resolved.

If, on the other hand, nothing can be done, the best course of action is likely just to edit them as you come across them. The last time something like this happened, it looks like the community was able to band together to get the job done, so an organised effort might be worthwhile if you were hoping to get it done sooner.

Unfortunately Data Explorer's current hardware appears to be insufficient for querying for the old URL against all of the post bodies on Stack Overflow, otherwise we could get a better feel for the scope of the issue. You can always just do a site search for the URL now that URL wildcards are supported, which I suppose makes more sense anyway.

  • Thanks for doing the proper thing and bringing it up on GitHub, I was too lazy ;) – TJB Oct 1 '13 at 3:50
  • Awesome, glad this got fixed! – TJB Oct 2 '13 at 17:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .