You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 23, 2024. It is now read-only.
While the change introduced in the PR: #749 was nice, it wasn't completely done, and now (after rebasing to the latest master), it produces many errors. I'm not sure if all the checks for bash scripts are required, perhaps some of them are "redundant" or just "too aggressive"... or perhaps we should just fix them one by one. For now, it is not our highest priority.
Besides, I'm not sure if tests on our CI were executed properly - my guess is the change around test.sh (which -> command -v to be precise) may lead to unexpected behavior. It would require some deeper diving into this problem.
The text was updated successfully, but these errors were encountered:
While the change introduced in the PR: #749 was nice, it wasn't completely done, and now (after rebasing to the latest master), it produces many errors. I'm not sure if all the checks for bash scripts are required, perhaps some of them are "redundant" or just "too aggressive"... or perhaps we should just fix them one by one. For now, it is not our highest priority.
Besides, I'm not sure if tests on our CI were executed properly - my guess is the change around
test.sh
(which
->command -v
to be precise) may lead to unexpected behavior. It would require some deeper diving into this problem.The text was updated successfully, but these errors were encountered: