Github Action Tutorial Feedback

[Oceanestars]

Hi!
Just finished the GitHub action tutorial which was my first ever exposure to GitHub actions(and my first course through GitHub skills)!
Workflow seems to closely relate to pipeline( is there a difference between the two?).

I have some feedback, hopefully, it's helpful :)(take however much you want)!

Pros:

• The number of resources provided was greatly appreciated.
• The amount of info and length of this was very easy.
• The format was very engaging.

Cons:

• I was left with a few questions
• Some steps were very high level. I know it's an introduction but I wish we would have gone over the things that were already given to me.

Suggestion:

• A quick walkthrough of the actions provided with the repo(Step 0 - 5)(beyond what's in the read me, for example, I went through the whole tutorial and I kept receiving the emails about the failing workflow but didn't fully understand and this sentence "and an action will automatically close this step and open the next one." didn't mean much until closer to the end. I recommend maybe pointing to "Step 1, Create a workflow" in the actions tab and point how the action closed the step inside the yaml file. (No need to do that for every step but having a little bit more context of what's happening at all times would be cool.

• A longer walkthrough of the actions tab. I found myself wondering why so many steps were failing (like Check emoji shortcode)

• Optionally, It could be cool if you made the course taker create a step 6 workflow and get them halfway to a more complicated way of maybe scheduling actions.

Overall, this was very enjoyable and I appreciate all the efforts put into this course!

[gmondello]

my experience is similar to @Oceanestars. Really enjoy the interactive nature of these tutorials. I think there may be a syntactical error in Line 7 of the yml file... and hopefully someone smarter than me can fix it :)

[dannymonareng]

I agree that most things are intimidating before you start, however after the first step you gain confidence and begin to enjoy the results.

[SuperRoach]

I think somethings wrong with the syntax - Like you're grepping for [^ -~] inside the readme.md file, adding a variety of emojis would error out - I copy and pasted a few 😐 like emoji which are not short code and think that was wrong compared to a :code: style one. I would suggest having another part that comments on say how large the file is, to prove something has changed as well.

[volksec]

It was a great experience!

[damitr]

I am not able to complete Step 2. substep 5. Commit your changes.
Though I am able to edit the _config.yml file, I am not able to commit changes. The commit changes button is not clickable and is grayed out. What could be the issue?

[gmondello]

can you add a screenshot here to make it easier to diagnose?

[damitr]

Here is the editor, as you can see the "Commit Changes" button is not enabled.

[yhakamay]

I enjoyed it, though I'm a kind of intermediate user. GitHub Actions for collapsing instructions were significant; I didn't even know that 😳

[xiganbana]

Like what we continue to learn every day ^^, otherwise very good course for beginners.

[pausad]

where is the training site ?

[Oceanestars]

Are you talking about this https://github.com/skills?

[NigelRowlan]

Step 2 - I cannot get this to work at all. In ci.yml -

Run npm install remark-cli remark-preset-lint-consistent

added 179 packages, and audited 180 packages in 6s
89 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
README.md
115:1-115:63 warning Emphasis should use _ as a marker emphasis-marker remark-lint
⚠ 1 warning

Error: Process completed with exit code 1.

And in the instructions, the english does not make sense -

"Update the code in the ci branch to get the test to pass. You need to look something like this:
underscore"

This is completely clueless and I'm giving up.

[mrpatricko]

I came here to make the same comment. I can't seem to fix the error either.

Can't we just see a screenshot of what we need to type in order to fix the error? "underscore" is so vague.

---

EDIT:

For anyone else that got stuck on step 2, you just need to goto line 115 in the README.md file and add an underscore to both ends of that line. (also delete the asterisk).

[Mbuyamba]

Thank you! Very helpful.

[Data-Engineer-Joe]

i can feel you! I was stuck for 2hours and had no clue! underscore didn't help anything. even step 1 was so unclear where to put things, even to find ci.yml. oh wait it's somewhere in some folders... uf

[ghost]

I really liked it nd It really helped me .

[Arzumtn]

Response

[Arzumtn]

Hi! Just finished the GitHub action tutorial which was my first ever exposure to GitHub actions(and my first course through GitHub skills)! Workflow seems to closely relate to pipeline( is there a difference between the two?).

I have some feedback, hopefully, it's helpful :)(take however much you want)!

Pros:

• The number of resources provided was greatly appreciated.
• The amount of info and length of this was very easy.
• The format was very engaging.

Cons:

• I was left with a few questions
• Some steps were very high level. I know it's an introduction but I wish we would have gone over the things that were already given to me.

Suggestion:

• A quick walkthrough of the actions provided with the repo(Step 0 - 5)(beyond what's in the read me, for example, I went through the whole tutorial and I kept receiving the emails about the failing workflow but didn't fully understand and this sentence "and an action will automatically close this step and open the next one." didn't mean much until closer to the end. I recommend maybe pointing to "Step 1, Create a workflow" in the actions tab and point how the action closed the step inside the yaml file. (No need to do that for every step but having a little bit more context of what's happening at all times would be cool.
• A longer walkthrough of the actions tab. I found myself wondering why so many steps were failing (like Check emoji shortcode)
• Optionally, It could be cool if you made the course taker create a step 6 workflow and get them halfway to a more complicated way of maybe scheduling actions.

Overall, this was very enjoyable and I appreciate all the efforts put into this course!

[jacobjauregui]

Wow!!! It was a challenge for me. But thanks to this I managed to learn much more about different really useful programming tools !!! 👍

[JirawatChanthamail]

M

[anhLd184032]

Good, study easily

[velazmatt]

genial

[epellejero]

Excelente !

[teboho]

Was a fun experience to go through! <3

[avilanicasionan92]

[avilanicasionan92]

Oli

[Irfanath]

I really like it! , first time i understand the purpose of Github and process. reaaly interesting!

[Techlearner08]

It's nice and clear, just need more practise to get familiar with each functions