@mcaceresb it would be great if you provided tags that correspond to the version number that is embedded. I've updated the README, but you may have to create the tags in your main repository, e.g.
git tag 1.1.0 77706f2702c43b63f2b427b6e281b286711a34c4
git push --tags
I ran into a problem where a researcher had used an earlier version, and the newer version didn't work with their code. Referencing the older commit worked, but commits are messy...
@mcaceresb it would be great if you provided tags that correspond to the version number that is embedded. I've updated the README, but you may have to create the tags in your main repository, e.g.
I ran into a problem where a researcher had used an earlier version, and the newer version didn't work with their code. Referencing the older commit worked, but commits are messy...