From the course: Learning GitHub Actions
Unlock the full course today
Join today to access over 24,200 courses taught by industry experts.
Add a metadata file - GitHub Tutorial
From the course: Learning GitHub Actions
Add a metadata file
- [Instructor] At this point, we have just about everything in place for our action. Now we can add metadata. The metadata will provide details about the action, and more importantly, it specifies the interfaces needed for the workflow environment to call the action successfully. We can include seven types of metadata for our action. Required metadata includes the action name, a description, the author of the action, and the specific commands needed to run the action. And I should say that the author isn't really required, but if you're writing a custom action, you should be proud to put your name on it. Other metadata that we can include, but isn't required, are inputs, outputs, and branding. GitHub uses Feather Icons to add icons to actions. On the Feather Icons website, we can see that there are hundreds of different icons to choose from. To find the right icon, we can use the search bar to filter things down a…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
-
-
(Locked)
Plan a custom action4m 28s
-
(Locked)
Your custom action objective1m 7s
-
(Locked)
Dockerfile review4m 58s
-
(Locked)
Add a Dockerfile2m 20s
-
(Locked)
Add an entry-point script2m 30s
-
(Locked)
Use runtime environment resources4m 11s
-
(Locked)
Test an action locally3m 52s
-
(Locked)
Complete the entry-point script2m 2s
-
(Locked)
Add a metadata file2m 48s
-
(Locked)
Add a README file1m 48s
-
(Locked)
Deploy a custom action2m 22s
-
(Locked)
Publish an action to the Marketplace4m 16s
-
(Locked)
Challenge: Create a custom action1m
-
(Locked)
Solution: Create a custom action7m 47s
-
(Locked)
-