Prevent adding a tool to a new panel if already present

[lldelisle]

I think it would be good that when a new tool is added, the CI checks that the tool is not already present into another yaml.

[bgruening]

We actually want to go the other direction and allow this explicity, so that every community can maintain and assemble their own toolset.

[lldelisle]

But what is the link between the tool panel and the community? The tool panel is used for subdomains?

[bgruening]

Yes thats the plan. I just want to finish the themeing deployment, until we touch the tool panel handling.
galaxyproject/ansible-galaxy#194

The idea is to use those yaml files here (at least partially) to define the tool panel and tool sections. Ideally, Every subdomain will have just its own default tool panel.

[lldelisle]

OK thanks for the explanations.