-
Notifications
You must be signed in to change notification settings - Fork 448
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
Circos and PR workflow fixes #5242
Circos and PR workflow fixes #5242
Conversation
Lets try :) Thanks for the suggestion. Wondering if it might be a solution to forbid tools-iuc/.github/workflows/pr.yaml Line 432 in 1d443e7
Somehow I remember that we added this only to allow for PR that do not change tools .. but this might be better solved by #5219 |
xref 4cc19b2 |
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.
looks fine for me
Not quite, I'm afraid. #5219 only serves as a shortcut for obvious cases of "no tool can possibly be affected by this". You can still have changes witihin tool directories that are not supposed to trigger tests. So #5219 can act as a prefilter that gets simple cases out of the way fast, but you still need the more fine-grained logic of the planemo action for everything that passes that first check. |
Do you have an example? |
Currently, the only example is changes to tools listed in .tt_skip. If we are talking about any skipped steps, not just planemo testing, something I'd like to implement soonish is skipping R linting when no R-related files have been touched. |
python restrictions should come via conda, removing it seems to allow to resolve the environment. also gawk seems not to be used in the tools, so it should come via conda. Co-authored-by: Nicola Soranzo <[email protected]>
And the last question before merging: should we bump? I would say no... |
FOR CONTRIBUTOR: