tool/pipeline wrapping FAQ #5374
Draft
Conversation
This file contains 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
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.
Adding some quick FAQs on pipeline/tool wrapping to help colleagues.
This is based on real world internal experiences trying to ship things that are needed on very tight deadlines. As such, I won't be accepting criticism that this advice isn't "best practice", yeah, obviously! It's a question of return on investment for certain valid internal use cases. And I think not everyone who uses galaxy knows that there are options if they need them. Suggestions for improving the snippets to make them more easily copyable and to have them approach better practices would of course be welcome!