Default extmodules workflow now treats all subdirs of MODULEPATH dirs… #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… as semantically important. Old behavior still available with "recursive" option.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses the issue from #2, with default behavior that treats each directory from the given MODULEPATH as the top level of a tree where everything below it is semantically significant (i.e. all subdirs are part of the module name). The old behavior is still available by using the --modules-recurse option for ipf_configure when configuring the workflow.
This default behavior no longer excludes module files that exist directly in the top level directory (as was the old default behavior). To keep this behavior, use the --ignore_toplevel_modulefiles when configuring the workflow.