the task: "Update the code in the ci branch to get the test to pass." Clue: on line 18 there is a file. the issue has something to do with markdown syntax. i personally asked chat gpt, and thats how i reached to the solution after a long time.. good luck!

The following line is causing the warning and error

npx remark . --use remark-preset-lint-consistent --frail

The "." is asking to check all files for markdown syntax and its warning that "resume.md" is not following the syntax.

You can use "" or "*" to markdown as italics font.
However when you use "consisent" as in the code above, then you should only use either "" or "" throughout the file.
"resume.md" started using "_" and then later it also used "", hence the warning.
(ref:https://www.npmjs.com/package/remark-lint-emphasis-marker/v/3.1.0)

The "--frail" will exits as failed when there is a warnings.
(ref: Search for "--frail" in the URL:https://github.com/remarkjs/remark-lint)

In short if you where to replace *Git* with _Git_ in the "resume.md" then you will not have any errors.

But then we don't get to do the LAB as per the instructions provided.

Also the error Screenshots mentioned in Step2 - "Review required" and "Merging is blocked" never occurs, as there were no Branch rules already to cause this error.

If at the beginning of the Step1, we add a step to create a branch rule requiring one reviewer approval then we get this error when attempting to perform the pull request after creating the ci.yml.

Linking issue #48

@skills/technical-reviewers Would ya'll mind taking a look at this one? 👀 👍

This error is intentional.

Even after the code is indented properly in ci.yml, you will see a build error in GitHub Actions. We'll fix this in the next step.

@sinsukehlab is right, but I agree that the instructions expect the learner to do a lot of heavy lifting with reading so I'll leave this open but it's feedback about the course structure mostly.

@sinsukehlab is right, but I agree that the instructions expect the learner to do a lot of heavy lifting with reading so I'll leave this open but it's feedback about the course structure mostly.

This error is intentional.

I don't think this is the issue. The main issue is that the Step 2 guide is written with a frame a reference that speaks to unit (or other tests), not linting. So the person trying to follow along is left wondering where the tests are - spoiler, there are none.

I'm guessing this tutorial was originally written using test failures/fixes, but then ported to linting at some point? If so, step 2 was never updated to talk about linting instead of testing - including the workflow failure screenshots, which still show a matrix run and test failures, which causes even more confusion.

@gradybarrett is right in pointing out that for a new learner it is difficult to find and fix errors by just looking at few lines of error message. There were no instructions to run the job in "debug mode" either.
Looking for "remake" run script errors is not the intention of this particular skills project.

The other relevant Bug for this issue that has not been discussed/included in above issue list is that the "Step 2: Fix the test" manual (see screen shot included below) does not specifically mention that the learner has to make changes in either file README.md or resume.md file of the "ci" branch. Only a change in these two files is factually/actually needed by the Step-2-workflow's (2-fix-the-test.yml) job trigger condition through push (commit in this case) user action/activity. Please refer to the screenshots for clarity.