The logic and commands for your custom action are defined in a script. In this lesson, develop the outline for the commands your script will run.
- [Instructor] At this point, … we've verified our script is working, … and we tested it with our docker file … using a sample JSON payload. … Let's take a look at the script … after it's been updated with code … that interacts with the GitHub API. … I'm viewing the entry script in Vim now, … and I have the line numbers turned on … to help with finding details in the script. … On line 23 we create a version variable. … We'll use that to name and tag the release. … On lines 25 through 29, we use the version variable … and printf statements to format a JSON string … and store that in a variable named data. … We'll be posting that data to the GitHub API … to create our release. … On line 31 we use the GitHub repository environment variable … to build the URL that we'll use to post to the API. … We also add the GitHub token environment variable … to the end of the file so our call to the API … can authenticate to our GitHub account. … Using these environment variables … keeps our script from having hard coded values. …
Author
Michael Jenkins
Released
2/21/2020- Creating an action
- Creating a workflow
- Adding actions to a workflow
- Using an action from a repository
- Developing a CI/CD pipeline with GitHub Actions
- Building custom actions
- Publishing an action to the GitHub Marketplace
Skill Level Beginner
Duration
Views
-
Introduction
-
What you should know1m 32s
-
Working with YAML files1m 25s
-
1. Your First Action
-
Your first Action2m 31s
-
-
2. Connecting Actions with Workflows
-
Create a workflow3m 11s
-
Add actions to a workflow4m 27s
-
Run a workflow2m 31s
-
Add conditions to a workflow2m 40s
-
-
3. Using Actions
-
Using secrets4m 1s
-
Using artifacts4m 7s
-
Manage pull requests3m 30s
-
4. Developing a CI/CD Workflow
-
Plan your CI/CD pipeline1m 53s
-
Linting and unit tests2m 7s
-
Testing1m 44s
-
Deploying1m 38s
-
-
5. Building Custom Actions
-
Plan a custom action4m 22s
-
Dockerfile review4m 58s
-
Add a Dockerfile2m 20s
-
Add an entry-point script2m 30s
-
Test an action locally3m 52s
-
Add a metadata file2m 50s
-
Add a README file1m 48s
-
Deploy a custom action2m 22s
-
-
Conclusion
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Complete the entry-point script