Implement shed_update to upload & update repo metadata.#216
Merged
jmchilton merged 2 commits intogalaxyproject:masterfrom May 21, 2015
Merged
Implement shed_update to upload & update repo metadata.#216jmchilton merged 2 commits intogalaxyproject:masterfrom
shed_update to upload & update repo metadata.#216jmchilton merged 2 commits intogalaxyproject:masterfrom
Conversation
Member
|
+1! |
Member
|
@jmchilton what's the timeline for the next planemo release? You've added a LOT of great shed interactivity lately |
Member
|
Wonderful! |
This should replace ``shed_upload`` in many potential workflows - but this does require a ``.shed.yml`` file with all metadata populated so ``shed_upload`` is still useful for directly uploading custom tar files for instance. I have filled out the documentation on ``shed_upload`` and ``shed_update`` to reflect this. Additionally, for consistency with the new ``shed_update`` operation - ``shed_create`` now also performs an upload in addition to simply populating the metadata for a new remote repository. The old behavior of ``shed_create`` can be obtained by supplying a new ``--skip_upload`` flag. ``shed_create`` can also take in a ``-m/--message`` option now as well to reflect this new behavior. Updated ``publish.rst`` to reflect these simplifications (the instructions are now easier).
8b49c71 to
0aaae9a
Compare
Member
Author
|
@erasche new planemo release should happen today or tomorrow. |
jmchilton
added a commit
that referenced
this pull request
May 21, 2015
Implement ``shed_update`` to upload & update repo metadata.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should replace
shed_uploadin many potential workflows - but this does require a.shed.ymlfile with all metadata populated soshed_uploadis still useful for directly uploading custom tar files for instance. I have filled out the documentation onshed_uploadandshed_updateto reflect this.Additionally, for consistency with the new
shed_updateoperation -shed_createnow also performs an upload in addition to simply populating the metadata for a new remote repository. The old behavior ofshed_createcan be obtained by supplying a new--skip_uploadflag.shed_createcan also take in a-m/--messageoption now as well to reflect this new behavior.Updated
publish.rstto reflect these simplifications (instructions now easier).Closes #199.