The comments below (under the heading "Commits") were part of commit messages, to help me test out how much gets included.
Although the GitHub web interface abbreviates long commit messages, the full commit message is included below for each.
However, for one of the commits, there is also a commit description, which is not included. So we should make sure that everything we want people to see in the automatically generated release notes is included in the commit message.
Users can read the description by clicking on the link to the commit or the pull request, but if we put anything in there, then the commit message should say something like "click on commit/PR for more details".
Commits
- [[167cc3c](https://github.com/UC-Davis-molecular-computing/scadnano/commit/167cc3ca1115baf5ed79164d9967786852f47a2e)]: bumped version from 0.9.2 to 0.9.3. There are no other changes with this, but I want to keep the version in line with the Python repo, and also test out the automatic releasing we are using on GitHub to make sure that it automatically includes this comment. (David Doty) [#326](https://github.com/UC-Davis-molecular-computing/scadnano/pull/326)
- [[3a26ef4](https://github.com/UC-Davis-molecular-computing/scadnano/commit/3a26ef41e386024c85e8f81f5aa2c690dbbfe022)]: This commit tests the commit messages. I want to see what happens when I have a long comment that GitHub abbreviates, to see if the comment makes it in to the release notes. This is the last sentence of the long top-level comment. (David Doty) [#326](https://github.com/UC-Davis-molecular-computing/scadnano/pull/326)