Course feedback

[cmwilson21]

We'd love to hear what you thought of this course! Please leave your feedback below and let us know!

[liebespaar93]

good github action! 🌈
go!! kyoulee! 🚀
42seoul~ is nice~ 🎓

[Julian-Dumitrascu]

We're looking for software with which to achieve many things. How is Microsoft going to help us?
Topic 1: Communication
1.1 We want to thread messages.
1.1.1 I've found one means: child issues.
1.1.1.1 I don't like it that we'd have to ask our conversation partners to work more than necessary.
Example: One has to create the issue as a task.
1.1.1.2 How are we going to let participants in a conversation (issue tree) enable / disable notifications about an issue being created in a tree or in certain branches of such a tree?
Can one write an action that causes notifications or builds something that causes notifications?
If yes, how does one learn how to write it?
I like it when you explain code and show what results one gets with it.

[monthviewsales]

Hi there, I seem to be stuck on step 5->6. I've created the branch test-workflow, made a change on it. PR'ed and merged it, but my readme isn't updating. When I look at the action, the merge step is being skipped, but I dont see why and its not an error so I dont know what to do.

[YunusOganPXL]

hey i m on step 5 i updated the readme.md file with an emoji and i started a pull request but nothing is happening im stuck ive refreshed the site multiple times but its not progressing

[PauliusVa]

There is a error in this:
Invalid workflow file: .github/workflows/welcome.yml#L1permissionsis not a valid event name

[LegacyUnix]

Hi @cmwilson21 thanks for posting this course. It was a great introduction to actions.

One interesting issue I experienced was a merge conflict, between my changes to README.md and the github-actions[bot] changes to the same file.

In step 4, the course guidance is:

1. Make a new branch named test-workflow.
2. Commit any change to your branch, such as adding an emoji to your README.md file.

as luck would have it, my change for adding emoji lines was adjacent to an action patch and caused the merge conflict 😄

To avoid this potential issue I would suggest the course advising the student to change files other than the ones the bots are changing (ie. README.md)

[ashley-aa511]

It was easy to manouvre around this course, easy to learn too.

[LucioMSP]

Excellent course!

[johnapaz]

The beginning of the course was a little tricky, mostly because I didn't wait the 20 seconds for my README to refresh, went in search of the actual instructions, then got turned around trying to follow the instructions from viewing the source code instead of the README. I got it figure out eventually, and everything worked as described. Good job, y'all!

[amitkumar-aimlp]

Great course; Keep up the nice work GitHub :)

[themakarrony]

Stuck in step 5 as well, followed every detail but readme does not update.

[prak112]

Amazing course and precise details to fulfil tasks! Thank you for the time and effort to make this beginner-friendly 👍🏾
If possible, I suggest giving a real-world example. For instance, triggering a workflow for automated pull-request merging after executing a basic test.
Either ways, this was very helpful! Hope I can implement build, test and deploy workflows from this and the documentation. Thanks a lot!

[AmauryVanEspen]

Hi @cmwilson21
the step by step introduction is nice,
2 pain points,

• first, the "next steps" is definitely not obvious
  a direct link to Automate workflows with GitHub Actions would help.
• there is no guidance about handling error and how to fix them,
  here an example of my own question about read/write persmission and how to handle issue with token permission.

Regards
Amaury