Connecting your figshare and Github account is the first step to archiving your Github repos in figshare so that they can be cited and reused along with any related datasets.

(info) Notes:


Steps:

Connect your GitHub account to Figshare

  1. Login to figshare, and under the My data tab click on the Octocat icon next to the Create a new item button. 
    Mousing over the icon will display the text 'Import from GitHub".

  2. Or....Login to figshare and click on your user icon in the upper right
    choose Applications from the menu that appears


    and then choose Connect under the GitHub Octocat icon
  3. If you are already logged into Github, it will prompt you to authorize figshare to access your account

  4. To turn on auto-sync, toggle the on/off "switch" in the resulting configuration window.
    If auto-sync is enabled, fighsare will automatically import a zipped file of your repo every time you publish a new version.
    Your figshare item will be versioned as well, so older zipped archives of your repo are accessible in both places.


(info) You can always leave syncing turned off, and selectively enable syncing for specific repos by

    1. Going to My data and check the box next to the figshare item that contains your repo
    2. change the toggle "switch" to on for that item

Import your repo

    1. If your GitHub account is already linked, click on the Octocat icon next to Create a new item

    2. check the box next to the repo you want to import - if there is no release, the latest commit will be chosen) then click the button to Import selected repos

    3. You will now be able to turn on syncing for that repo, and add metadata and reserve a DOI by clicking the Add info button

      Alternately, you can Close this window and add metadata later. Your unpublished item will appear with your other datasets in the My data tab.
      Simply follow the steps to Describe your data (add metadata) as you would for any other dataset.
      (info) Figshare automatically characterizes your imported repo as software, and selects SI's preferred Apache2.0 license for software.