Summary
In this module, you implemented a CI solution using GitHub Actions and workflows.
You can now:
- Build and test a Node.js project by using GitHub Actions and a templated workflow
- Debug a failed test using the GitHub Actions log
- Customize your workflow with GitHub Actions to:
- Create a build artifact and save it
- Get access to your build artifacts
- Test against multiple targets
- Add labels to your pull requests
Next steps
To continue your journey with GitHub Actions, check out the next module on this learning path, where you'll expand on what you have learned here and use GitHub Actions for continuous delivery and implementing infrastructure as code.
Learn more
Here are some links to more information on the topics we discussed in this module.
- GitHub Actions documentation
- GitHub Marketplace
- GitHub created actions
- actions/checkout@v3
- actions/upload-artifact
- actions/download-artifact
- pullreminders/label-when-approved-action
- Metadata syntax for GitHub Actions
- Workflow syntax for GitHub Actions
- Events that trigger workflows
- GitHub Actions usage limits
- About GitHub Actions: Job
- About CI: Job
- npm install
- npm run
- npm test
- Default environment variables
- Contexts
- Essential features of GitHub Actions
- Using the cache action
- Passing data between jobs in a workflow
- Enabling debug logging
- Using workflow run logs
- Workflow runs