Add GitHub Actions as a supported form of Continuous Integration (CI)

[DilumAluthge]

GitHub Actions will reach general availability on November 13. It would be great if, by that date, PkgTemplates was able to set up GitHub Actions for continuous integration (CI).

Unfortunately, I know very little about GitHub Actions. But I know that @davidanthoff has been working on Julia + GitHub Actions. Maybe he can provide some guidance.

[christopher-dG]

That should be an easy deadline to hit, seeing as https://github.com/julia-actions has most of the work done.

[davidanthoff]

I think we are still trying to figure out the best way to do this with GitHub Actions, any feedback on what we have so far would be great!

[christopher-dG]

Sounds good, I'll have a look and open issues if I notice anything.

[DilumAluthge]

@christopher-dG Out of curiosity, will PR #61 fix this issue?

[carstenbauer]

Since I couldn't find it in the docs, is it now possible to set up GitHub workflow based CI through PkgTemplates?

[christopher-dG]

On master branch; I need to re-add the interactive code before tagging a new release.
You can browse docs for #107 here, which is master + TagBot + CompatHelper.

[carstenbauer]

AFAICS, there is no support for Github CI + custom registry, though. Basically the latter simply requires an extra step in the workflow:

- name: Add CustomRegistry
  run: julia -e 'using Pkg; Pkg.Registry.add(Pkg.RegistrySpec(url="http://github.com/JuliaRegistries/General")); Pkg.Registry.add(Pkg.RegistrySpec(url="http://github.com/owner/CustomRegistry")); Pkg.Registry.status()'
  shell: bash

Note that one has to set shell: bash as otherwise Windows runs will fail. Also, one cannot test on Julia < 1.1 this way, since, as has been pointed out by @DilumAluthge above, the Pkg.Registry stuff requires Julia >= 1.1.

Should I open a separate issue for this?

[christopher-dG]

You're right, that support isn't there right now (but the file argument is as a stopgap).
Good idea to open a new issue.

[NHDaly]

Now that it's been a while, can we set the GitHub Actions CI as one of the default plugins that get added to every package?

[nickrobinson251]

Now that it's been a while, can we set the GitHub Actions CI as one of the default plugins that get added to every package?

Seems reasonable to me! Made an issue to track it #357

Can you be tempted to make a PR, @NHDaly ?

[NHDaly]

Thanks! 😅 probably not in the next few weeks. maybe i'll have a look again after that if I am available. Feel free to ping me if nothing happens on that other issue. Hopefully a new contributor is excited to tackle it themselves! 😁