Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

A workflow for the entire team #4

Open
github-learning-lab bot opened this issue May 1, 2020 · 0 comments
Open

A workflow for the entire team #4

github-learning-lab bot opened this issue May 1, 2020 · 0 comments

Comments

@github-learning-lab
Copy link
Contributor

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 master branch can't be deleted or inadvertently broken
  • 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

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

  1. Edit your existing workflow file in a new branch
  2. In that file, target versions 8.x and 10.x of Node, only
  3. Open a new pull request titled Improve CI for your change.

I'll respond when you open the pull request.

This was referenced May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants