A workflow for the entire team

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
github-actions, javascript, nodejs
Domain
ci-cd

Research direction

Read the existing .github/workflows/node.js.yml workflow linked in the issue. Update its build targets to Node.js 12.x and 14.x only, then open a pull request titled “Improve CI” to confirm the workflow change is complete.

Written by the indexing model from the issue text.

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:

an icon of three gears

Test against multiple targets so that we know if our supported operating systems and Node.js versions are working

icon of gears indicating relationship between multiple jobs

Dedicated test job so that we can separate out build from test details

icon of a binary file

Access to build artifacts so that we can deploy them to a target environment

icon of a security shield indicating branch protections

Branch protections so that the main branch can't be deleted or inadvertently broken

icon of a review approval

Required reviews so that any pull requests are double checked by teammates

icon of a review approval

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 12.x and 14.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.

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from molnar-atesz/github-actions-for-ci

All issues in molnar-atesz/github-actions-for-ci

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.