GitHub Actions at Work
Using your first GitHub Action
GitHub Actions can feel daunting. Here's a walkthrough setting up your first action that runs some command line scripts on every push to master.
Instructor: [00:00] To set up our first GitHub action and use it, we'll first create a new repo. After we create our first repository, we can get to the actions by clicking on the Actions tab. GitHub has provided a set of starter workflows under the Action's namespace.
[00:18] You can see that this workflow in particular echoes "Hello, World!" and then echoes two more lines. It also uses the Action's checkout action, which comes from the same Action's namespace. We'll choose to set up this workflow.
[00:34] We'll give our workflow a name. We can see that it's fired on every push. It runs on Ubuntu, the latest, and it has the same steps that we looked at before. We'll commit this. Now we'll go back into the Actions tab. Notice that no workflows have yet been run. After cloning the repository, we can find our workflow in .github/workflows/echo-content.yml.
[01:05] We'll create a README and add it to our repo. Now that we've pushed to our repo, we can see our action running. Note that we can see the logs in real time.
Member comments are a way for members to communicate, interact, and ask questions about a lesson.
The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io
Be on-Topic
Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.
Avoid meta-discussion
Code Problems?
Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context
Details and Context
Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!