-
Notifications
You must be signed in to change notification settings - Fork 10
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
First draft of GitHub Actions #161
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.
this looks good to me,
how is the action triggered in response to for example modifications to the ingestion tutorial yml ?
Any commit pushed to the main branch or in a pull request to the main branch triggers this action. |
To clarify: any file edited in the repo, even if irrelevant to the ingestion tutorial triggers this workflow. Basically, when we'll have multiple workflows, they will all be triggered when anything changes. |
the question is actually the other way around. any changes here (https://github.com/DendrouLab/panpipes) trigger the action. |
Changes in the tutorial repo won't trigger the action, no. It wouldn't make sense anyway, as the action doesn't run the contents of the tutorial repo itself, but rather my adaptation of it into a workflow in the YAML format required by GitHub actions. |
ok thanks for clarifying! |
Goes without saying but updating the input files on figshare also wouldn't trigger the action. |
No description provided.