Skip to content

Commit c10de73

Browse files
authored
Update create-custom-github-action.md
@lavanyanooka @erich-infomagnus @sivakinfomagnus @byron-infomagnus @RinatS line 36, is where we want the updates for 3.1.4 and 3.1.5 sub OD. Line 132 is where we want updates for 3.1.2 and 3.1.3 to go.
1 parent abf93e2 commit c10de73

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

learn-pr/github/create-custom-github-actions/includes/create-custom-github-action.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,10 @@ The steps to build a JavaScript action are minimal and straightforward:
3333

3434
Composite run steps actions allow you to reuse actions by using shell scripts. You can even mix multiple shell languages within the same action. If you have many shell scripts to automate several tasks, you can now easily turn them into an action and reuse them for different workflows. Sometimes it's easier to just write a shell script than using JavaScript or wrapping your code in a Docker container.
3535

36+
<!-- INFOMAGNUS UPDATES for 3.1.4 and 3.1.5 go here. Source Material for 3.1.4 : https://docs.github.com/en/enterprise-cloud@latest/actions/sharing-automations/creating-actions/creating-a-composite-action#creating-a-composite-action-within-the-same-repository
37+
38+
Source Material for 3.1.5 : https://docs.github.com/en/enterprise-cloud@latest/actions/sharing-automations/creating-actions/developing-a-third-party-cli-action ->
39+
3640
## Metadata and syntax needed to create an action
3741
3842
When creating or reviewing a GitHub action, a great first step is to review the `action.yml` file to assess which inputs, outputs, description, runs, and other configuration information the action needs. Some of these parameters are required, while others are optional. The `action.yml` file defines the following information about your action:
@@ -125,6 +129,8 @@ runs:
125129
shell: bash
126130
```
127131
132+
<!-- INFOMAGNUS UPDATES for 3.1.2 and 3.1.3 go here. Suggested Source Material : https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/about-troubleshooting-workflows ->
133+
128134
### Branding
129135
130136
An optional but fun feature is the ability to customize the badge of your action. The badge is displayed next to the action name in the [GitHub Marketplace](https://github.com/marketplace?type=actions). You can use a color and [Feather](https://feathericons.com/) icon to create the badge. For branding, you'll need to specify the icon and color you wish to use.

0 commit comments

Comments
 (0)