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: workflow-templates/check-shell-task.md
+60Lines changed: 60 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,30 @@ Install the [`check-shell-task.yml`](check-shell-task.yml) GitHub Actions workfl
23
23
24
24
The formatting style defined in `.editorconfig` is the official standardized style to be used in all Arduino tooling projects and should not be modified.
25
25
26
+
### Configuration
27
+
28
+
Configure the paths of the shell scripts to be checked as elements in the [job matrices](https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix) of `check-shell-task.yml` at:
29
+
30
+
-`jobs.lint.strategy.matrix.script[]`
31
+
-`jobs.formatting.strategy.matrix.script[]`
32
+
-`jobs.executable.strategy.matrix.script[]`
33
+
34
+
#### Example:
35
+
36
+
```yaml
37
+
matrix:
38
+
script:
39
+
- path/to/some-script.sh
40
+
- path/to/another-script.sh
41
+
```
42
+
43
+
#### Paths filters
44
+
45
+
The workflow is configured to be triggered on changes to any files in the repository that have a `.sh` or `.bash` file extension. If the project contains shell scripts without a file extension, the path to those scripts must be added to the following keys in `check-shell-task.yml`:
46
+
47
+
- `on.push.paths[]`
48
+
- `on.pull_request.paths[]`
49
+
26
50
### Readme badge
27
51
28
52
Markdown badge:
@@ -64,3 +88,39 @@ On every push or pull request that modifies one of the shell scripts in the repo
64
88
- Runs [`shfmt`](https://github.com/mvdan/sh) to check formatting.
65
89
- Checks for forgotten executable script file permissions.
66
90
```
91
+
92
+
## Usage
93
+
94
+
In addition to the automated checks provided by the GitHub Actions workflow, the tasks can be ran locally.
95
+
96
+
### Prerequisites
97
+
98
+
The following development tools must be available in your local environment:
0 commit comments