Open bitsgalore opened 1 year ago
Tried updating pre-commit-hooks to latest version:
https://github.com/openpreserve/jpylyzer/commit/3aa8aae3406d28e66276f57b4516e493c762c008
Pushing changes doesn't trigger new Travis build. Perhaps @darrendignam or @carlwilson could have a look at this some time (I don't really understand Travis that well)?
Hi @bitsgalore how would you feel about moving the build to GitHub actions instead? We're now using that for most of our projects, it's a bit more modular and flexible, it's also quicker. If you're happy I'll get this done in the next weeks.
@carlwilson Fine with me, thanks for looking into it!
Looking at the Travis results of the latest builds (most recent one here), it looks like something goes wrong setting up the environment for the pre-commit command. See Travis output starting at:
https://app.travis-ci.com/github/openpreserve/jpylyzer/jobs/587417609#L424
And the root cause appears to be:
https://app.travis-ci.com/github/openpreserve/jpylyzer/jobs/587417609#L446
The pre-commit-hooks version is defined here. The 1.4.0 version specified there is pretty old (latest version is 4.3.0).