I added a gitignore file so the temporary files won't clutter the repository, are easily removed, and won't accidentally committed.
I standardized formatting in the README. Replaced carriage returns with newlines and things like that. Also I wrapped all the lines at 80 characters; this has no impact on the compiled HTML, but makes reading easier for people in text editors. I can revert this if you like.
The biggest change is that addition of continuous integration with Travis. Most major repositories on github now use Travis (or a similar service) to tell users whether a given commit/version builds successfully and passes whatever tests the developers subject the code to. If you jump over to my fork, you'll see a little green shield above the README that says "build passing". You can adapt the .travis.yml file to run whatever tests you like.
You will need to update the first line in the README to point to your repository. Just replace the line with this:
These are all pretty minor changes.
I added a gitignore file so the temporary files won't clutter the repository, are easily removed, and won't accidentally committed.
I standardized formatting in the README. Replaced carriage returns with newlines and things like that. Also I wrapped all the lines at 80 characters; this has no impact on the compiled HTML, but makes reading easier for people in text editors. I can revert this if you like.
The biggest change is that addition of continuous integration with Travis. Most major repositories on github now use Travis (or a similar service) to tell users whether a given commit/version builds successfully and passes whatever tests the developers subject the code to. If you jump over to my fork, you'll see a little green shield above the README that says "build passing". You can adapt the .travis.yml file to run whatever tests you like.
You will need to update the first line in the README to point to your repository. Just replace the line with this:
[](https://travis-ci.org/bioinfologics/satsuma2)