E1 - GitHub Actions: Write your first workflow with GitHub APIs || Beginner friendly tutorial

This is the first video of the series: "GitHub Actions: Full Course" and in this one you'll get your hands dirty with building your first workflow and learning all the fundamentals of working with GitHub Actions.

We will cover how the internals of GitHub Actions, workflow syntax, jobs, steps, functions, conditionals, community actions, log viewer, and I will be showing you step by step how you can use GitHub Actions to call GitHub's REST APIs to automate certain tasks!

▬▬▬▬▬▬ Resources & References 📕 ▬▬▬▬▬▬

▬▬▬▬▬▬ Timestamps 🕐 ▬▬▬▬▬▬
00:00 - Intro
02:17 - Overview of GitHub Actions
05:15 - Workflow syntax
18:11 - GitHub web editor & syntax validation
20:10 - Building the issue comments workflow
23:53 - Using a community action
26:08 - Using GitHub REST APIs in workflows
30:47 - Conclusion

▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ Support the channel 💜 ▬▬▬▬▬▬

Every little bit helps ✨

#devops #githubactions #softwareengineering

[drakhakami]

if you are getting the following error when you run these aciton codes; Resource not accessible by integration. Following these steps may solve the problem.
1- Go to repository "Settings".
2- After that it will show you a left pane where you will find "Actions"
3- Expand "Actions" tab
4- Click on "General" under options tab.
5- Now on new page scroll down and you will fine "Workflow Permissions"
6- Select "Read and Write" under "Workflow Permissions".

[specthanatos]

Been browsing through Udemy courses, but this one is just way better. Fast and clear, good simple examples!

[sukhwinder]

Whiteboarding is really good before starting topic discussion. Missed by many other well renowned content creators, Kudos to that.

[JARVIS-CHEN]

really thankful, it is really helpful to a graduate who really want some hands-on experience in real industry

[abedalrawas]

This was very well articulated and packed with information. Crystal clear.Thank you!

[GautamKhatter]

Your intro music really motivated me. This is the first time I was so excited for a coding video.

[sacktrac]

Awesome job here - really appreciate it. You're a wonderful instructor.

[hassansalem]

I think this will be a great and very useful series.
I really would like to learn how we can run a single job if it failed, instead of running the whole thing from scratch. Of course if that is possible, and if it is not possible, why not?🤔.
And really thanks for sharing the knowledge

[anthonyhaddad]

Been waiting for this series
Thank you Bassem!

[et]

I actually appreciate you getting deeper into it!

[salborough]

This video was brilliant and so well presented - thank you so much :)

[bokistotel]

If someone gets " Resource not accessible by integration! " error when using auto-generating comment, it means your permissions are not right. You can add in comments-with-action: permissions: write-all

[GidiBaum]

👍Very nice explanation, Greeting from Haifa

[karmansingh]

Would have wanted to know what caused the error and how you resolved it in the end. Specially for people like me who like to code along :)
Thank you for the video, psyched for the rest of the videos in the series too!

[Vityashortsstudio]

Aug 2023 - for me worked v2 for comment + added permissions: write-all

[ahmedouyahya]

Thanks a lot, Bassem. It's very information dense.
I laughed when I saw you testing it with: LAST LAST LAST/ LAST LAST LAST LAST LAST/ Really Last.

[lorenzopieri]

Nice playlist and videos! Thanks for sharing :)

[basheeral-momani]

I think I should subscribe, thanks a lot for this in depth information

[matthewheimerdinger]

looking at the gist... ah, yeah, I was wondering if the organisation/organization thing was going to be a problem. Hooray, English! =D

[onticmix]

Why wouldn't you show how you debugged the error? When someone is following along it is rather frustrating to see a time-lapse and "magic" it works. At least tell us what you did to fix the errors. I caught a few of them but keep getting a "You have an error in your yaml syntax on line 31". Thanks for taking the time to put something like this together though.