Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit bb5eb31

Browse files
committed
Update README.md
1 parent 2e24590 commit bb5eb31

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ What this does
88

99
This is a proof of concept integration between a GitHub repo and Figshare in an effort to get a [DOI](http://en.wikipedia.org/wiki/Digital_object_identifier) for a GitHub repository. When a repository is tagged for release on GitHub Fidgit will import the release into Figshare thus giving the code bundle a DOI. In a somewhat meta fashion, Fidgit is publishing itself to Figshare. Its DOI is [http://dx.doi.org/10.6084/m9.figshare.828487](http://dx.doi.org/10.6084/m9.figshare.828487).
1010

11-
Fidgit isn't really designed for 'production' use for example there's little or no error handling but hopefully there's some value here.
11+
Fidgit isn't really designed for 'production' use, for example there's little or no error handling but hopefully there's some value here.
1212

1313
How it does it
1414
--------------
@@ -93,6 +93,6 @@ If everything goes to plan then these tasks should run without error and should
9393
That's a wrap!
9494
--------------
9595

96-
And that's about it. If you now create a new release on GitHub then you should see this code bundle being mirrored to your specified location on Figshare. Check out the [Fidgit one here](http://dx.doi.org/10.6084/m9.figshare.828487). Any questions, comments, concerns post and issue.
96+
And that's about it. If you now create a new release on GitHub then you should see this code bundle being mirrored to your specified location on Figshare. Check out the [Fidgit one here](http://dx.doi.org/10.6084/m9.figshare.828487). Any questions, comments, concerns post an issue.
9797

9898
![DOIed](https://raw.github.com/arfon/fidgit/master/screens/figshare_article.png)

0 commit comments

Comments
 (0)