You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-25Lines changed: 8 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,12 +26,6 @@ Write your own GitHub JavaScript Action and automate customized tasks unique to
26
26
-**What you'll learn**: How to consume actions within a workflow file, create custom JavaScript based actions and publish your newly created action to the marketplace.
27
27
-**Prerequisites**: Before you start, you should be familiar with GitHub, GitHub Actions, and Continuous Integration with GitHub Actions.
28
28
-**How long**: This course is 6 steps long and takes about 1 to 2 hours to be completed.
29
-
30
-
## Projects used
31
-
32
-
This makes use of the following open source projects. Consider exploring these repos and maybe even making contributions!
33
-
34
-
-[GitHub Actions Toolkit](https://github.com/actions/toolkit), a multipurpose JavaScript library for writing actions
35
29
36
30
## How to start this course
37
31
@@ -55,17 +49,6 @@ This makes use of the following open source projects. Consider exploring these r
55
49
Encourage users to open new tabs for steps!
56
50
TBD-step-1-notes.
57
51
-->
58
-
### Welcome to this Skills course about Actions where you will build the following:
59
-
60
-
-
61
-
62
-
- In this course you will build three actions that each accomplish different tasks designed to demonstrate the flexibility of creating and consuming JavaScript Based Actions.
63
-
64
-
- First, you will start with the traditional "Hello World!" program which will teach you where to find the output of a workflow run. You will then modify this "Hello World!" action to accept `input` parameters which allow the action to be more dynamic.
65
-
66
-
- Second, you will write an action that call upon an external API to retrieve a fact about cats and prints it to the workflows output. You will then modify this cat fact action to set the retrieved data as `output` for another action in the workflow to consume.
67
-
68
-
- Lastly, you will write a third action that will open an issue in your repository making the cat fact available to everyone. You will learn how to use the `output` of previous actions as `input` for current actions in this step.
69
52
70
53
### Configuring a workflow
71
54
@@ -79,9 +62,9 @@ _In our case, we will use this one **workflow** file for many things, which lead
79
62
80
63
Read more about [workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/configuring-a-workflow#choosing-the-type-of-actions-for-your-workflow)
81
64
82
-
<detailsid=1open>
65
+
<detailsid=1close>
83
66
84
-
<summary><strong> Step 1: Initialize a new JavaScript project</strong></summary>
67
+
<summary><h2> Step 1: Initialize a new JavaScript project</h2></summary>
85
68
86
69
## On to your development environment
87
70
@@ -148,7 +131,7 @@ Once you have the necessary tools installed locally, follow these steps to begin
148
131
</details>
149
132
150
133
<details id=2>
151
-
<summary><strong> Step 2: Configure Your Action</strong></summary>
134
+
<summary><h2> Step 2: Configure Your Action</h2></summary>
152
135
153
136
### Excellent!
154
137
@@ -183,7 +166,7 @@ We will start with using the parameters that are **required** and later implemen
183
166
</details>
184
167
185
168
<details id=3>
186
-
<summary><strong> Step 3: Create the metadata file</strong></summary>
169
+
<summary><h2> Step 3: Create the metadata file</h2></summary>
187
170
188
171
## Action metadata
189
172
@@ -240,7 +223,7 @@ Our action does not require much metadata for it to run correctly. We will not b
240
223
</details>
241
224
242
225
<details id=4>
243
-
<summary><strong> Step 4: Create the JavaScript files for your action</strong></summary>
226
+
<summary><h2> Step 4: Create the JavaScript files for your action</h2></summary>
244
227
245
228
## Files
246
229
@@ -402,7 +385,7 @@ _Don't forget to call the `run()` function._
402
385
</details>
403
386
404
387
<details id=5>
405
-
<summary><strong> Step 5: Add your action to the workflow file</strong></summary>
388
+
<summary><h2> Step 5: Add your action to the workflow file</h2></summary>
406
389
407
390
### Great job!
408
391
@@ -438,7 +421,7 @@ jobs:
438
421
439
422
<details id=6>
440
423
441
-
<summary><strong> Step 6: Trigger the joke action</strong></summary>
424
+
<summary><h2> Step 6: Trigger the joke action</h2></summary>
442
425
443
426
### Great job!
444
427
Everything is all set up and now we are ready to start laughing. You will find you have some joke related labels available to you in this repository. You don't have to use them, any label will trigger our workflow, but the easiest way to follow along would be to use suggested labels.
@@ -453,7 +436,7 @@ Everything is all set up and now we are ready to start laughing. You will find y
453
436
</details>
454
437
455
438
<details id=7>
456
-
<summary><strong>Finish</strong></summary>
439
+
<summary><h2>Finish</h2></summary>
457
440
458
441
### Congratulations, you've completed this course!
0 commit comments