-
Notifications
You must be signed in to change notification settings - Fork 85
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
Elevate missing .shed.yml to error #708
Conversation
How will this interact with recursion and different levels of testing for tools? e.g. |
http://galaxy-iuc-standards.readthedocs.io/en/latest/best_practices/repositories.html#github-repositories according to this, suites should be in a separate directory, which sidesteps the problem ;) But yes, you raise a good point. I don't have a good answer for this, and I'm open to ideas. I just believe that a missing .shed.yml is |
I agree this is important, and as long as it doesn't break existing widespread folder structures, its a very good thing. Planemo already has some non |
I was a bit confused by this at first - because I thought planemo defines a repository as a directory containing a
This behavior is because of the last line here. I really was trying to take a very light touch with .shed.yml files originally and everything in there truly was optional - non-optional fields could be specified at the command-line for instance. With that in mind, two things.
Therefore - I think the existing INFO or WARN would be correct - the problem is that you are linting in such a way that you are explicitly ignoring warnings. I think it would be better to just fail on warnings as is the planemo default. I've opened a tools-iuc PR here galaxyproject/tools-iuc#1407 that would cause metadata problems with repositories to fail the build while still "ignoring" warnings in the tools themselves - I think that is better right? |
From #107 (comment)
This change will probably cause repositories which passed linting before, to fail now, if people were passing directories which weren't things which should be uploaded to the tool shed. Is that acceptable, or should this be hidden behind a strictness falg or something?