We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Now that we've learned how to quickly set up CI, let's try a more realistic use case.
Our fictional team has a custom workflow that goes beyond the template we've used so far. We would like the following features:
Test against multiple targets so that we know if our supported operating systems and Node.js versions are working
Dedicated test job so that we can separate out build from test details
Access to build artifacts so that we can deploy them to a target environment
Branch protections so that the main branch can't be deleted or inadvertently broken
main
Required reviews so that any pull requests are double checked by teammates
Obvious approvals so we can merge quickly and potentially automate merges and deployments
Can GitHub Actions support this workflow? Let's find out. We'll tackle some of the changes to the existing workflow file first.
12.x
14.x
I'll respond when you open the pull request.
The text was updated successfully, but these errors were encountered:
Merge pull request #4 from githubtraining/dependabot/npm_and_yarn/htt…
879483c
…p-proxy-1.18.1 Bump http-proxy from 1.18.0 to 1.18.1
No branches or pull requests
Custom workflow
Now that we've learned how to quickly set up CI, let's try a more realistic use case.
Our fictional team has a custom workflow that goes beyond the template we've used so far. We would like the following features:
Test against multiple targets so that we know if our supported operating systems and Node.js versions are working
Dedicated test job so that we can separate out build from test details
Access to build artifacts so that we can deploy them to a target environment
Branch protections so that the
main
branch can't be deleted or inadvertently brokenRequired reviews so that any pull requests are double checked by teammates
Obvious approvals so we can merge quickly and potentially automate merges and deployments
Step 7: Create a custom GitHub Actions workflow
Can GitHub Actions support this workflow? Let's find out. We'll tackle some of the changes to the existing workflow file first.
⌨️ Activity: Edit the existing workflow with new build targets
12.x
and14.x
of Node, onlyI'll respond when you open the pull request.
The text was updated successfully, but these errors were encountered: