Skip to content
We Sort.

GitHub Successor settings

In GitHub there is an option to configure a ‘successor’. This is intended for managing the code portion of an estate when someone dies. I’ve done this reciprocally with a close friend who also works with GitHub.


From GitHub’s Copilot when I asked how this works (as there wasn’t great docs on it already):

Short answer: a successor cannot log into your account and cannot gain automatic full control of private repositories. Successors are intended to manage only public repositories (archive or transfer them); managing private repositories requires GitHub Support and additional legal verification and isn't automatic.

How it works and the process

  • Invite a successor:

    1. Go to Settings → Account.

    2. Under "Successor settings", begin typing a username, full name, or email, select the user, and click Add successor.
      (See Maintaining ownership continuity of your personal account's repositories.)

  • What a successor can do by default:

    • Archive your public repositories.

    • Transfer your public repositories to their own user account.

    • Transfer your public repositories to an organization where they can create repositories.
      Successors cannot log into your account. (From Personal repository access and collaboration.)

  • If the account holder is deceased:

    • A designated successor (or other authorized individual) can request further actions through GitHub Support. To request access or repository transfers after death, GitHub may require documentation (for example, a death certificate or obituary) and then apply waiting periods (7 days after a death certificate, 21 days after an obituary) before allowing successor-managed actions for public repositories. Contact GitHub via the GitHub Support portal to start this process. See the GitHub Deceased User Policy and the maintaining ownership continuity doc for details.

  • About private repositories:

    • The documentation specifies successor actions for public repositories only. Private repositories are not listed as transferable by a successor by default. Any request to manage or transfer private repositories will require contacting GitHub Support and providing proof/authorization; GitHub will evaluate and may require legal documentation. (See [Maintaining ownership continuity…] and GitHub Deceased User Policy.)

Other notes

  • Invitation events are recorded in the security log (successor_invitation.create/accept/cancel).

  • To proceed with any successor-requested actions after death, contact GitHub Support and include the requested identifying and relationship information as outlined in the Deceased User Policy.

Relevant docs:

s-2x2-01
tf-2x2-01
s-2x2-01
ht-2x2-01