FizzBuzz791 / FizzBuzz791/github-actions-for-ci

A workflow for the entire team

Open
#4 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

# 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.

### :keyboard: Activity: Edit the existing workflow with new build targets

1. Edit your [existing workflow](https://github.com/FizzBuzz791/github-actions-for-ci/edit/master/.github/workflows/nodejs.yml) 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.