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
If this action finds no autogen.sh, or configure, or make file, etc, should it fail?
I think this could be potentially helpful.
A CI workflow for a package that does not require compilation does not need to call this Action.
On the other hand, I have encountered situations before where I have not quite set up the CI correctly, which has meant that this Action cannot find the relevant autogen.sh etc file, which meant that the package has not been compiled. Nevertheless, this Action still passed according to the CI (and it was only on studying the log that I could see what was going on).
If this action finds no
autogen.sh
, orconfigure
, or make file, etc, should it fail?I think this could be potentially helpful.
A CI workflow for a package that does not require compilation does not need to call this Action.
On the other hand, I have encountered situations before where I have not quite set up the CI correctly, which has meant that this Action cannot find the relevant
autogen.sh
etc file, which meant that the package has not been compiled. Nevertheless, this Action still passed according to the CI (and it was only on studying the log that I could see what was going on).For me, this is similar to gap-actions/run-pkg-tests#8
The text was updated successfully, but these errors were encountered: