A logic to trigger tasks with extensionless files #1184
Unanswered
eandersons
asked this question in
Q&A
Replies: 1 comment 2 replies
-
|
The answer depends from task to task: Depending on what options are available, this is already possible. You can choose not to provide |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
There may be cases when extensionless files have to be checked by specific tasks, but I did not manage find how to get the files without extension to trigger tasks.
A couple of use cases with extensionless files:
bin/is expected all files to be shell scripts, and they should be checked with shell task (for example, with shellcheck);app/bin/is expected to have PHP executables that should be checked as PHP files;Dockerfiles also have linting tools,, so it would be quite safe to assume that files in specific directories or with specific name are of certain type.
Can tasks be triggered by extensionless files with the current functionality?
If not, probably a new option (
triggered_by_globsortriggered_by_patterns) which would accept values likebin/*,app/bin/*orDockerfilecould be added, but I am not sure how well that would fit with the current implementation of file filtering.A possible workaround is to add extension to all those files, but there are cases when executable files have to be extensionless (for example, the task
doctrine_ormexpects the executable filedoctrineto be found). A workaround to that would be to create a symbolic link (for example:ln -s doctrine.php doctrine).I would rather not use such workarounds, but it does not seem that currently I have other options.
Beta Was this translation helpful? Give feedback.
All reactions