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

[18.01] Workaround for extra metadata revision creation #5433

Merged
merged 1 commit into from Feb 1, 2018

Conversation

Projects
None yet
4 participants
@davebx
Contributor

davebx commented Feb 1, 2018

Without this change, uploading non-metadata changes to a toolshed repository will display an error message and create a new metadata revision regardless of whether the code should determine that a new metadata revision is warranted.

Workaround for extra metadata revision creation
Without this change, uploading non-metadata changes to a toolshed repository will display an error message and create a new metadata revision regardless of whether the code should determine that a new metadata revision is warranted.
@mvdbeek

mvdbeek approved these changes Feb 1, 2018

@mvdbeek mvdbeek changed the title from Workaround for extra metadata revision creation to [18.01] Workaround for extra metadata revision creation Feb 1, 2018

@mvdbeek mvdbeek added this to the 18.01 milestone Feb 1, 2018

@martenson martenson merged commit 6b0542f into galaxyproject:release_18.01 Feb 1, 2018

6 checks passed

api test Build finished. 344 tests run, 4 skipped, 0 failed.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
framework test Build finished. 171 tests run, 0 skipped, 0 failed.
Details
integration test Build finished. 79 tests run, 4 skipped, 0 failed.
Details
selenium test Build finished. 118 tests run, 4 skipped, 0 failed.
Details
toolshed test Build finished. 577 tests run, 0 skipped, 0 failed.
Details
@martenson

This comment has been minimized.

Member

martenson commented Feb 1, 2018

Thanks @davebx !

@davebx davebx deleted the davebx:release_18.01 branch Feb 1, 2018

@dannon

This comment has been minimized.

Member

dannon commented Feb 13, 2018

This fixed #5425

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment