Using Julia in GitHub Actions

Tooling
,
22

@ctkelley Sorry, I’m not sure. The only thing that looks off to me is

which maybe should be release-*? I’m not totally sure though.

23

Just tried release-*. Didn’t break anything, but also did not work.

24

Found this
https://github.community/t/github-actions-does-not-respect-skip-ci/17325/8
and used one of the ideas in the middle of the thread. It seems to work

jobs:
  build:
    runs-on: ${{ matrix.os }}
    if: "!contains(github.event.head_commit.message, 'skip ci')"

I’m moving my CI to GitHub Actions today and we’ll see if it works there too. Most of what I read says that it will.

25

Just switched to GitHub actions for Ci and @ericphanson 's solution suddenly worked! This makes sense in hindisight. So the skip ci koan’s been solved. Ooooooom!

3 Likes
26

A quick heads-up for everyone who pins julia-actions/setup-julia to either a specific version or a commit sha: GitHub removed a deprecated and exploitable way of setting environment variables and adding to the PATH in Actions. All setup-julia versions < 1.3.1 were broken by that. If you’re seeing build failures, you need to update to a more recent version of the setup-julia action, at least 1.3.1.

If you use a version like julia-actions/setup-julia@v1 or julia-actions/setup-julia@latest, you don’t need to do anything.

As a quick workaround, you can also set a secret ACTIONS_ALLOW_UNSECURE_COMMANDS to true but for security reasons, this is not recommended.

2 Likes