How do GitHub Actions work?

Most straightforward explanation wins 🤪

Comments

[Adrien Gallouët]

There's nothing straightforward than an example, the last one I wrote: github.com/angt/secret/blob/master...

[Taufik Nurrohman]

It’s just some do_action('push') stuff within the GitHub’s WordPress site environment.

We then do some add_action('push', function() {}) stuff to listen to the push event through our WordPress plugin for GitHub.

🤐

[drewmullen]

Not an explanation but here's a bunch of working examples different action workflows! github.com/drewmullen/actions-play...

[Victoria Drake]

When a GitHub event you've defined happens, someone else's computer does whatever you've told it to do.

[Sarthak Sharma]

I was thinking to create a series for this on Dev and you gave me another reason for it. 😅

[Conlin Durbin]

Run a Docker container or Node script with access to your code when something happens on Github.

[Wassim Chegham]

With GitHub Actions you can react to events (anything that happens on GitHub) and run command (Actions). See it as the Event Driven pattern applied to modern DevOps.

[Sharad Raj (He/Him)]

They work well 😂

[Glenn Carremans]

Travis CI on steroids? 🤔

[Tierney Cyren]

Serverless in GitHub that's free for Open Source.