How to move/rename an existing set of documentation?

mlang's Avatar


09 Jul, 2020 05:06 PM

We recently renamed to AND we changed the default branch from `master` to `main`

What's the best way to move all existing documentation from:
* (master)

* (main)

  1. Support Staff 1 Posted by lsegal on 09 Jul, 2020 05:12 PM

    lsegal's Avatar

    Your documentation should exist at both locations and reflect the current state of each git repository. If GitHub is redirecting rpm to newrelic-ruby-agent under the hood, these two URLs will be equivalent, so there really isn't anything to "move" per se.

    If URL redirection is what you're looking for, this is something you probably want to do in your own URL links. Unfortunately, RubyDoc doesn't handle redirections for old repositories.

  2. 2 Posted by mlang on 09 Jul, 2020 07:54 PM

    mlang's Avatar

    Ok, allowing the links to live for both the old repo name and new is good enough as will redirect the old links to the new links.

  3. 3 Posted by mlang on 09 Jul, 2020 07:54 PM

    mlang's Avatar

    Do we need to add the repository again with it's new name or is that automatic?

  4. Support Staff 4 Posted by lsegal on 09 Jul, 2020 07:55 PM

    lsegal's Avatar

    You certainly would, but it looks like it's already setup:

  5. 5 Posted by mlang on 09 Jul, 2020 11:45 PM

    mlang's Avatar

    Wow, that's amazing! Gotta love Ruby and the folks building tools that
    Just Works(tm) with it!


  6. Support Staff 6 Posted by lsegal on 10 Jul, 2020 12:35 AM

    lsegal's Avatar


    No thank you!

  7. lsegal closed this discussion on 10 Jul, 2020 12:35 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac