Skip to content
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

Update README.md #354

Merged
merged 4 commits into from
Jul 29, 2020
Merged

Update README.md #354

merged 4 commits into from
Jul 29, 2020

Conversation

JTrentSmart
Copy link
Contributor

Adding BibTex citations to the GitHub ReadMe

Pull Request Checklist

  • Merge in the latest Develop branch changes to your branch
  • Remove .pyc files from your repository:
    • Linux/Mac
      • find . -name *.pyc -delete
    • Windows
      • del /S *.pyc
  • Run automatic regression and makes sure everything is passing
  • Did you make a new regression test that covers your new code?
  • Did you update your docstrings?
  • Did you update your headers to include your name and date?
  • Do a final compare with the Develop branch to be sure what you're changing

Adding BibTex citations to the GitHub ReadMe
@planes
Copy link
Member

planes commented Jun 8, 2020

I like the idea of explicitly explaining how to cite SUAVE. I think we should ask the full crew and figure out what we want as our preferred citation. We have the Zenodo link on the top right now that makes a bibtex to our DOI (it goes to SUAVE 2.0 right now), but maybe it's not clear to use that. I like that it sets an exact version of the code. But maybe should we prioritize publications?

@coveralls
Copy link

coveralls commented Jun 12, 2020

Coverage Status

Coverage remained the same at 86.699% when pulling 5322878 on Github-Readme-Citation into 1ebb9b3 on develop.

@JTrentSmart JTrentSmart merged commit 639bbc8 into develop Jul 29, 2020
@JTrentSmart JTrentSmart deleted the Github-Readme-Citation branch July 29, 2020 05:40
@planes planes mentioned this pull request Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants