By providing sections of the .shed.yml like
- repository type (yuck, so galaxy specific)
- synopsis
- detailed description
- categories
we can encode useful metadata about a tool in a re-usable and versioned manner, and it would allow us to do automatic repository creation if the target doesn't exist. (If there's a name and owner specified in the .shed.yml, there is, IMO, no reason to not automatically create that repository.)
By providing sections of the
.shed.ymllikewe can encode useful metadata about a tool in a re-usable and versioned manner, and it would allow us to do automatic repository creation if the target doesn't exist. (If there's a name and owner specified in the .shed.yml, there is, IMO, no reason to not automatically create that repository.)