|
1 | | -# Create a JavaScript Action |
2 | | - |
3 | | -<p align="center"> |
4 | | - <a href="https://github.com/actions/javascript-action/actions"><img alt="javscript-action status" src="https://github.com/actions/javascript-action/workflows/units-test/badge.svg"></a> |
5 | | -</p> |
6 | | - |
7 | | -Use this template to bootstrap the creation of a JavaScript action.:rocket: |
8 | | - |
9 | | -This template includes tests, linting, a validation workflow, publishing, and versioning guidance. |
10 | | - |
11 | | -If you are new, there's also a simpler introduction. See the [Hello World JavaScript Action](https://github.com/actions/hello-world-javascript-action) |
12 | | - |
13 | | -## Create an action from this template |
14 | | - |
15 | | -Click the `Use this Template` and provide the new repo details for your action |
16 | | - |
17 | | -## Code in Main |
18 | | - |
19 | | -Install the dependencies |
20 | | - |
21 | | -```bash |
22 | | -npm install |
23 | | -``` |
24 | | - |
25 | | -Run the tests :heavy_check_mark: |
26 | | - |
27 | | -```bash |
28 | | -$ npm test |
29 | | - |
30 | | - PASS ./index.test.js |
31 | | - ✓ throws invalid number (3ms) |
32 | | - ✓ wait 500 ms (504ms) |
33 | | - ✓ test runs (95ms) |
34 | | -... |
35 | | -``` |
36 | | - |
37 | | -## Change action.yml |
38 | | - |
39 | | -The action.yml defines the inputs and output for your action. |
40 | | - |
41 | | -Update the action.yml with your name, description, inputs and outputs for your action. |
42 | | - |
43 | | -See the [documentation](https://help.github.com/en/articles/metadata-syntax-for-github-actions) |
44 | | - |
45 | | -## Change the Code |
46 | | - |
47 | | -Most toolkit and CI/CD operations involve async operations so the action is run in an async function. |
48 | | - |
49 | | -```javascript |
50 | | -const core = require('@actions/core'); |
51 | | -... |
52 | | - |
53 | | -async function run() { |
54 | | - try { |
55 | | - ... |
56 | | - } |
57 | | - catch (error) { |
58 | | - core.setFailed(error.message); |
59 | | - } |
60 | | -} |
61 | | - |
62 | | -run() |
63 | | -``` |
64 | | - |
65 | | -See the [toolkit documentation](https://github.com/actions/toolkit/blob/master/README.md#packages) for the various packages. |
66 | | - |
67 | | -## Package for distribution |
68 | | - |
69 | | -GitHub Actions will run the entry point from the action.yml. Packaging assembles the code into one file that can be checked in to Git, enabling fast and reliable execution and preventing the need to check in node_modules. |
70 | | - |
71 | | -Actions are run from GitHub repos. Packaging the action will create a packaged action in the dist folder. |
72 | | - |
73 | | -Run prepare |
74 | | - |
75 | | -```bash |
76 | | -npm run prepare |
77 | | -``` |
78 | | - |
79 | | -Since the packaged index.js is run from the dist folder. |
80 | | - |
81 | | -```bash |
82 | | -git add dist |
83 | | -``` |
84 | | - |
85 | | -## Create a release branch |
86 | | - |
87 | | -Users shouldn't consume the action from master since that would be latest code and actions can break compatibility between major versions. |
88 | | - |
89 | | -Checkin to the v1 release branch |
90 | | - |
91 | | -```bash |
92 | | -git checkout -b v1 |
93 | | -git commit -a -m "v1 release" |
94 | | -``` |
95 | | - |
96 | | -```bash |
97 | | -git push origin v1 |
98 | | -``` |
99 | | - |
100 | | -Note: We recommend using the `--license` option for ncc, which will create a license file for all of the production node modules used in your project. |
101 | | - |
102 | | -Your action is now published! :rocket: |
103 | | - |
104 | | -See the [versioning documentation](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md) |
105 | | - |
106 | | -## Usage |
107 | | - |
108 | | -You can now consume the action by referencing the v1 branch |
109 | | - |
110 | | -```yaml |
111 | | -uses: actions/javascript-action@v1 |
112 | | -with: |
113 | | - milliseconds: 1000 |
114 | | -``` |
115 | | -
|
116 | | -See the [actions tab](https://github.com/actions/javascript-action/actions) for runs of this action! :rocket: |
| 1 | +# Install GStreamer GitHub Action |
| 2 | + |
| 3 | +This action installs GStreamer by leveraging the release binaries for a specific version found here: |
| 4 | + |
| 5 | +``` |
| 6 | +https://gstreamer.freedesktop.org/data/pkg/ |
| 7 | +``` |
| 8 | + |
| 9 | +Supported runner environments are Windows and macOS. |
| 10 | + |
| 11 | +## Inputs |
| 12 | + |
| 13 | +### `version` |
| 14 | + |
| 15 | +The version of GStreamer to install. The default is 1.18.4. |
| 16 | + |
| 17 | +### `arch` |
| 18 | + |
| 19 | +The architecture (`x86` or `x86_64`) of binaries to install. |
| 20 | + |
| 21 | +## Outputs |
| 22 | + |
| 23 | +### `gstreamerPath` |
| 24 | + |
| 25 | +The installation path. |
| 26 | + |
| 27 | +## Example Usage |
| 28 | + |
| 29 | +In this example, it is a Windows environment and we want to set the `GSTREAMER_...` environment variables in a follow-on step. The first step runs the installation. The second step echoes the output variables from the previous step into variables that are then redirected into the `GITHUB_ENV` variable. If a next job were specified, it would have those variables set. |
| 30 | + |
| 31 | + |
| 32 | +``` |
| 33 | +- name: Setup GStreamer |
| 34 | + id: setup_gstreamer |
| 35 | + uses: blinemedical/setup-gstreamer@1.0 |
| 36 | + with: |
| 37 | + version: '1.19.90' |
| 38 | + arch: 'x86' |
| 39 | +- run: | |
| 40 | + chcp 65001 #set code page to utf-8 |
| 41 | + echo ("GSTREAMER_1_0_ROOT_MSVC_X86=${{ steps.setup_gstreamer.outputs.gstreamerPath }}") >> $env:GITHUB_ENV |
| 42 | +- run: | |
| 43 | + echo $env:GSTREAMER_1_0_ROOT_MSVC_X86 |
| 44 | +``` |
| 45 | + |
| 46 | +See the `.github/workflows/test.yml` for other examples. |
| 47 | + |
| 48 | +------------- |
| 49 | +**References:** |
| 50 | + * [Custom Actions](https://docs.github.com/en/actions/creating-actions/about-custom-actions) |
| 51 | + * [Action Toolkit](https://github.com/actions/toolkit) |
| 52 | + |
0 commit comments