differentiate skip files for workflows and tests #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm currently working on a PR that adds the reusable workflows from here to this repo
Obviously I would like to use these workflows itself in the tests running in this repo. This is complicated by any additional steps in the jobs, like those that exclude the test tools from workflow tests and tests workflows from tool tests.
planemo-ci-action/.github/workflows/tools.yaml
Line 120 in 5362f82
My suggestion is to differentiate between skip files for workflows and tools (then we can have both in this repo).
... the other open question is how to deal with the mock changes happening here ... but maybe we can leave this job as it is .. will think about it.