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.

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

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

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

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

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.

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.

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

@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

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

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

Thanks for sharing! I started looking a bit more into GitHub actions, yesterday

Love it! Straight and concise! Thank you!

Top-notch tutorial, as always 👏

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❤

Great video! Taught me enough to get automation on.

Cool, I understood some of the words in this one!

The github YAML files look beautiful, very intuitive.

Best video, so far !!!

I knew about GH actions but I never knew about act! Thanks

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

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.

Thank you for nektos/act.

Super awesome 😎 and informative. Thanks a lot!

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

right when i needed it!

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

Master branch keep the faith brother

I just love your content. ❤

Love your videos bro. Thanks.

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

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!

I didn't know about `act`. That's cool.

Thank you so much for this

watched it now, got the basic idea but im currently not using or planning to use or learn it now. I'll be back soon :)

Great video, Jeff! 🔥 Was so great to learn about act - I looked for a solution like this a while back and couldn't find anything. Quick question though: Is there any specific reason for using v2 over v3 of actions/checkout and action/setup-node?

I will debug myself to learn more from you

very wise indeed

ooh damn, thats very cool!

tx! awesome video..

Beyond programming

Wright timing. ✅

svelte is gold but react is gem!

I've been doing some GitHub actions with install-nix-action and then running 'nix build' which covers all dependencies and declaratively builds the project. Maybe you can make a video on nix next.

so many fancy names and tools

For an 'automated' solution that sure sounds complex and convoluted.

6:13 I fucking love cron magic strings, this for sure won't backfire in the future.

This is truly great but I just wish there was a feature that would automate that one thing I need to manually do every day at my current project

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.

8.5k views, 685 likes but only 25 comments (as of the time writing this) I really appreciate your videos and content, so here, take this free comment to sacrifice to the algorithm gods.

Hey) The video is awesome))) Thank you. I have a question thought: In a github issue page there s a button "create branch" (inside the Development section of the right panel). Is there a way to trigger an action that changes a state of the corresponding issue to inProgress when a branch is created using this button? I use github project to manage issues. Its awesome too)

7:58 a use case for self-hosted runners is if you run docker containers on a vps and want to automate the creation of images without having to git pull and run the commands yourself every time

Good enough for me

Thanks

0:06 is my life motto

謝謝分享

hi I noticed that you use v2 actions that produce tons of warnings about nodejs deprecating, can you use v3?

Do GitLab next? Would help a lot of us which have Corporate GitLab servers

sick

I can't believe I didn't know about act

Thanks. Didn't know Act before, so every time I want to change the workflow I have to wait for the whole run like an idiot.

Have you had any experience shortening that feedback loop earlier on the process, let's say at the pre-commit timeframe? I ask because we would commit things up to the repo to fire off a pipeline and then get fredback a few minutes later. It felt nicer (to me) to abort our commit if our tests, or linting failed. Yes there is always the option to force it through, but I liked that immediate feedback locally before something small and dumb was sent up.

Please make a video about auto merging

Github action ftw

you mean you don’t have like dozen of commits “CI TEST”? would love a breakdown on that act tool!

How do you automate versioning? Do you have to version bump manually in yml with each release?

Could you do some dewops stack?

I have used github actions to trigger tests on every push. But I experienced very slow behavior. Even for a very small small project it took tens of minutes to complete. Is it normal to take so long?

I disagree with npm CI for these. I use pnpm and cache the store (and even node modules itself) to speed up actions (cache key is the package-lock hash) Npm is slow, and CI prevents any caching options.

Please make a video about web componend

You have both main and master branches? What is this madness branching strategy? :))

Please make a video about nx

I wonder how firebase functions are work with GitHub actions?

Hey fireship do tutorials on legend state for react

what I don t like about Github Actions is that it doesn t support yml aliases which makes the file quite cluttered for big ci cds pipelines

0:00 that sound make subwoofers hit me in the back. aa

If I give gpt the link of the video can build the app automatically?

Is it possible to configure github actions to auto deploy to a custom server instead of big company servers like azure or aws?

Where was written the playwright test code? I only saw you linking it to the actions or something like that, but you never made the code that makes the test. I don't get it.

Brb gonna write-up a guide on Github Actions, am not gonna plow through life without a CI/CD engine

CV/Resume Skills: Ci/CD expert

Im starting with CI/CD

Could you please do a video on free tools and services? It would be very handy after the death of heroku

I gave up on making some ai that reads the code / commit messages and finds relevant memes to it and adds it to the or description

~kiiji

is act stable now? I had so many bad experiences with it in the past :(

All good practices, but these can be achieved with a number of SaaS CI/CD tools, not just github actions.

Dude, I need your jokes workflow!!!

idk i just use the google action lol aka release please

I don't think it's technically true that GitHub spins up a container when you start a workflow. I believe they connect you to a full VM.

something important missing, you should have explain how to deploy the code on your production machine upon code push.

Man, this AI voice is good!

It's drone CI all the way for me.

thanks

I think I heard the basement slaves at 7:32 doing animations for the daily code reports

I wonder whether anyone has setup completely standardized projects for use cases like "Python3 in a Docker image", including GitHub actions, linting and testing and whatnot.

Act is not working on M1 macbook.

Use ASDF instead of node setup

Make GitHub Actions with AWS ECS with EC2

need forgejo video. gitea with actions