-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.2 docs update #233
0.2 docs update #233
Conversation
…pdate # Conflicts: # The-SMIRNOFF-force-field-format.md # docs/releasehistory.rst # openforcefield/tests/test_forcefield.py
…pdate # Conflicts: # README.md # The-SMIRNOFF-force-field-format.md
This pull request fixes 1 alert when merging eaaf7db into 32273d5 - view on LGTM.com fixed alerts:
Comment posted by LGTM.com |
@jchodera -- Remaining questions not addressed in comments above:
Good idea. I went ahead and did it.
I'm ambivalent, but haven't thought too hard about this. Added to openforcefield/standards#48. We can make this its own issue if it builds traction. |
This pull request fixes 1 alert when merging 3f184a1 into 32273d5 - view on LGTM.com fixed alerts:
Comment posted by LGTM.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like you're good to go!
This pull request fixes 1 alert when merging e2d76b4 into 32273d5 - view on LGTM.com fixed alerts:
Comment posted by LGTM.com |
This PR does a lot of housekeeping, including:
0.2.0
0.2
/topology
urls with ones tolatest
andmaster
New docs can be found here: https://open-forcefield-toolkit.readthedocs.io/en/0-2-docs-update/