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

New datacheck to ensure consistency between... #109

Merged
merged 1 commit into from
Jun 10, 2019

Conversation

james-monkeyshines
Copy link
Contributor

... the species.production_name and the database name. This is a convention, that shouldn't be violated without good reason; but it's not something we want to enforce, so it's advisory.

…me and the database name. This is a convention, that shouldn't be violated without good reason; but it's not something we want to enforce, so it's advisory.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 482

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 98.119%

Totals Coverage Status
Change from base Build 467: 0.0%
Covered Lines: 1774
Relevant Lines: 1808

💛 - Coveralls

@james-monkeyshines james-monkeyshines merged commit 3990a6d into master Jun 10, 2019
@james-monkeyshines james-monkeyshines deleted the new_datacheck/db_species_name branch June 10, 2019 08:41
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.

None yet

3 participants