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.

Sign up for GitHub

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

Jump to bottom

a dataset is always uptodate if there is no frequency #2208

Merged
merged 2 commits into from
Jun 21, 2019
Merged

a dataset is always uptodate if there is no frequency #2208

merged 2 commits into from
Jun 21, 2019

Conversation

taniki
Copy link
Contributor

@taniki taniki commented Jun 21, 2019

FIX #916

@taniki taniki marked this pull request as ready for review June 21, 2019 14:47
@taniki taniki requested a review from a team June 21, 2019 14:48
@taniki taniki merged commit 971eca3 into opendatateam:master Jun 21, 2019
@taniki taniki deleted the fix/admin-quality branch June 21, 2019 14:59
@abulte abulte mentioned this pull request Jun 26, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@noirbizarre noirbizarre noirbizarre approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Admin: the up-to-date entry within the quality block is wrong
2 participants
@taniki @noirbizarre