You can get set up in the Applications section, also located in the dropdown menu at the top right corner next to your name. Next, select Connect as shown below:
You’ll be redirected to sign in to your Github account where you’ll authorise figshare.
Click off the Configure Github Integration overlay, go to My Data and click on the GitHub icon (that shows up after hovering the cursor on the Github symbol):
You can then start importing from GitHub from your list of public repositories:
If your repository has multiple releases, you can choose which is the first release you’d like to import. You can choose to select multiple items at the same time and each GitHub item will create it’s own figshare item.
Upon import, we will automatically choose the article type, add a reference back to the original GitHub item, import the description and title from GitHub and set the default licence to MIT.
A key aspect of setting Github up via the applications section is that you can edit the auto-sync global settings for your github integration. If you configure the auto-sync setting to ON, figshare will automatically update for every release (for each of your imported repos) and this will only occur if your figshare item is public. Each new release would generate a new version of your figshare item.
Please note: figshare will only create a new version for a release and not a single commit.
If you have something to upload straight away you can access the Github integration directly from My Data. From My Data, select Import from GitHub, as shown above. Then select Connect and you'll see an overlay with the public repositories available to import.
To help automate the publication step in GitHub-based research workflows, we've released the Figshare upload GitHub Action.
You can incorporate the upload Action in your GitHub workflows and push your files into Figshare directly from GitHub. For details regarding the Action setup visit the GitHub repo page at https://github.com/figshare/github-upload-action.
Can’t find your answer here, check the community discussion or raise a support ticket.
Share this article: