CI for Node

[zmajeed]

No description provided.

[github-learning-lab]

The title of this pull request isn't what I expected!

To rename your pull request:

1. Click on Edit next to the pull request's title.
2. The title will turn to a text field, CI for Node in the title field.
3. Click Save.

I'll respond when I detect this pull request has been renamed.

[github-learning-lab]

The title of this pull request isn't what I expected!

To rename your pull request:

1. Click on Edit next to the pull request's title.
2. The title will turn to a text field, CI for Node in the title field.
3. Click Save.

I'll respond when I detect this pull request has been renamed.

[github-learning-lab]

The title of this pull request isn't what I expected!

To rename your pull request:

1. Click on Edit next to the pull request's title.
2. The title will turn to a text field, CI for Node in the title field.
3. Click Save.

I'll respond when I detect this pull request has been renamed.

[github-learning-lab]

Templated workflow success!

Great job adding the templated workflow. Adding that file to this branch is enough for GitHub Actions to begin running CI on your repository. This takes a couple of minutes, so let's take this opportunity to learn about some of the components of the workflow file you just added. We'll dive deeper into some of the key elements of this file in future steps of the course.

Step 2: Run a templated workflow

I'll respond when GitHub Actions finishes running the workflow. You can follow along in the Actions tab, or by clicking Details on the pending status below.

---

Actions workflow not running? Click here

When a GitHub Actions workflow is running, you should see some checks in progress, like the screenshot below.

If the checks don't appear or if the checks are stuck in progress, there's a few things you can do to try and trigger them:

• Refresh the page, it's possible the workflow ran and the page just hasn't been updated with that change
• Try making a commit on this branch. Our workflow is triggered with a push event, and committing to this branch will result in a new push
• Edit the workflow file on GitHub and ensure there are no red lines indicating a syntax problem