Most straightforward explanation wins đ€Ș
For further actions, you may consider blocking this person and/or reporting abuse
Most straightforward explanation wins đ€Ș
For further actions, you may consider blocking this person and/or reporting abuse
Olukayode Asemudara -
dev.to staff -
Liubov Vas -
dev.to staff -
Latest comments (24)
There's nothing straightforward than an example, the last one I wrote: github.com/angt/secret/blob/master...
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 thepush
event through our WordPress plugin for GitHub.đ€
Not an explanation but here's a bunch of working examples different action workflows! github.com/drewmullen/actions-play...
When a GitHub event you've defined happens, someone else's computer does whatever you've told it to do.
I was thinking to create a series for this on Dev and you gave me another reason for it. đ
Run a Docker container or Node script with access to your code when something happens on Github.
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.
They work well đ
Travis CI on steroids? đ€
Serverless in GitHub that's free for Open Source.
GitHub has webhooks for tons of things that happen to your repo. GitHub actions lets you run whatever code you want (like unit tests!), to respond to any of those webhooks.
Your code runs on GitHub's servers and you can get status updates on whether your code passed or failed
commit -> event fired-> go through github action workflow file -> check the rules -> do the job
Github runs the job on runner you have mentioned like linux, mac or windows.
Event-based webhooks designed to automate your project's workflows - from issues tracking to deployments. Aaaaand, it's free for open source software.
Basically, a world-class CI/CD inside your repo.
Start a computer in the cloud each time [an action] is executed.
An action is triggered by an event. An event is and interaction with your repo on github. Itâs like saying âHey GitHub, when this thing happens can you do some stuff for me?â The âstuffâ is the set of instructions that you would like completing. An example would be to deploy when a commit is added on the master branch.