You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering, firstly if there would be any objections, and secondly, if anyone has any tips on implementing it? From the point of view of the CI it would be adequate to just add a maintainers field to the YAML files, which can be read whenever a new PR is opened. On the other hand it might be preferable to integrate this field directly into the Galaxy code. In the latter case, I guess the correct place to start would be https://github.com/galaxyproject/galaxy/blob/dev/lib/tool_shed/webapp/model/__init__.py#L182?
(hit submit too soon)
The text was updated successfully, but these errors were encountered:
For the autoupdate PRs (see galaxyproject/tools-iuc#3533) it would be nice to be able to ping one or more tool maintainers to review the changes. This would require a way to associate GitHub users as maintainers with a tool, similar to how they are listed in bioconda recipes (e.g. https://github.com/bioconda/bioconda-recipes/blob/master/recipes/spades/meta.yaml#L73). I assume the most sensible way is to add a field to the
.shed.yml
files.I am wondering, firstly if there would be any objections, and secondly, if anyone has any tips on implementing it? From the point of view of the CI it would be adequate to just add a
maintainers
field to the YAML files, which can be read whenever a new PR is opened. On the other hand it might be preferable to integrate this field directly into the Galaxy code. In the latter case, I guess the correct place to start would be https://github.com/galaxyproject/galaxy/blob/dev/lib/tool_shed/webapp/model/__init__.py#L182?(hit submit too soon)
The text was updated successfully, but these errors were encountered: