How GitHub Actions 10x my productivity

Learn how to use GitHub actions continuous integration and delivery in a software development project. In this quick tutorial, we look at 7 powerful ways to automate code with CI/CD.

#programming #automation

[StefanoV]

Great video! I didn't know about Act, I'm gonna install it RN.

I would like to add:
I recommend using paths-ignore (inside push and below branches) to trigger a specific workflow only when a specific path is involved.
For example if the docs folder is another project, if you push a readme update inside the project, all the workflow will run test again wasting you free minutes. With paths-ignore you can specify which path to ignore.

[snowdane]

The timing of this tutorial... I've been meaning to use GitHub actions to maintain a npm package... This couldn't have come out at a better time

[Sefton.]

This is my favourite type of content, covering stuff nearly every developer uses or should be using and showing tips, tricks etc.

[kevinandeleven]

Hosted runners are life savers.. I basically use them for all my server work.. Once🎉 I push code, a self hosted runner running on the servers pulls the changes and restarts the server

[roaringfork]

Github Actions actually spins up a whole vm. There are very specific circumstances in which this is important as I spent two weeks learning.

[NaveenKumar-nwre]

Currently working on setting CI/CD on a project. what a time to upload the video👌

[arjix]

@Beyond Fireship Actually, if the project repo is public, then the workflows are free w/o limit (other than the 6 hour limit that all workflows have)
the 2000 free minutes are for private repositories

[alanscodelog]

I've been using this setup (actions/act) but with semantic-release for a while. It's perfection. Don't even have to think about bumping versions / changelogs / publishing. Also you can create a little workflow badge to put on the repo or to keep a link to. Nice for having an overview of the state of several repos.

[tomchapman]

The selfhosted runners are super easy to set up, i did it and that way you also dont hsve any rate limits!

[JavArButt]

Within the first 16 seconds, I had to laugh/smile multiple times. Your sense of humor is great. Also, the time and deep thoughts you spend int this work is clearly visible.

[mattd]

I had no idea something like act existed, you just saved me a shit ton of time!

[flyingpanhandle]

I like to use Volta in my projects, handily you can then use Volta in your GHA pipeline. No need to specific node or npm/pnpm/yarn versions any more. It will use exactly the version the project was developed on. Which is fantastic when upgrading node version.

[Malephex]

I can't tell you how much time I've wasted in the past, pushing 1 byte changes to make a CI pipeline run while debugging the flow, all the time wishing I could just run the damn yaml/json/whatever file locally to simulate the CI/CD server ... thanks for the "act" tip!

[wlockuz]

Calling it life-saver is an understatement to be honest.

[emanuelescarsella]

I would have liked a video like this when I first learned GitHub actions, but still now I have to configure a new more complex project so that's still a good timing for me❤

[tyreldelaney]

I did not know about the act package, that's a pretty nifty tool

[georgiosmylonas]

Love it! Straight and concise! Thank you!

[Kaszanas]

I use a slightly different approach where I run a container inside GitHub Actions and run all of the commands against that container which acts as a development container too. So I achieve a couple of things at the same time. I do not need act to test my actions because all of the logic behind my actions is containerized anyway.

[abhishekshah]

I had act but never knew how to use it right! Thanks for showing us!

[thesleepykoala]

I like that fact he is smart and advertises his products.