-
Notifications
You must be signed in to change notification settings - Fork 4
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
Move Galaxy tools to the eBCSgen repository #118
base: ebcsgen-3.0
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't want to move Galaxy tools here - only the top-level API functions (.py
files). All the XML files, test data, or shed file don't belong here. And also it does not belong to Galaxy subdirectory (this should be actually removed one day when all "local" issues are resolved - e.g. properly sharing visualisations).
Thank you for your feedback regarding the structure of the repository. I have made the necessary changes as per your suggestions. Moved the top-level API functions to directory in the root of this repository (commit 5eca9c2) and removed all xml files, test data and the Galaxy subdirectory, ensuring that only the relevant Python files remain (commit 5eca9c2). |
This is a good start, but I would improve it in following ways:
|
Moved the top-level API functions from the galaxytools repository to
/api
directory in this repository, the eBCSgen repository.No modifications were made to the scripts or the original repository.
Close #115