|
10 | 10 | steps:
|
11 | 11 | - uses: actions/checkout@v2
|
12 | 12 | - uses: Arduino-CI/[email protected] # or latest, or a pinned version
|
13 |
| - env: |
14 |
| - # Not all libraries are in the root directory of a repository. |
15 |
| - # Specifying the path of the library here (relative to the root |
16 |
| - # of the repository) will adjust that. |
17 |
| - # |
18 |
| - # The default is the current directory |
19 |
| - # |
20 |
| - USE_SUBDIR: . |
21 |
| - |
22 |
| - # Not all libraries include examples or unit tests. The default |
23 |
| - # behavior of arduino_ci is to assume that "if the files don't |
24 |
| - # exist, then they were not MEANT to exist". In other words, |
25 |
| - # if you were to accidentally delete all your tests or example |
26 |
| - # sketches, then the CI runner would by default assume that was |
27 |
| - # intended and return a passing result. |
28 |
| - # |
29 |
| - # If you'd rather have the test runner fail the test in the |
30 |
| - # absence of either tests or examples, uncommenting either of |
31 |
| - # the following lines (as appropriate) will enforce that. |
32 |
| - # |
33 |
| - EXPECT_EXAMPLES: true |
34 |
| - EXPECT_UNITTESTS: false |
35 |
| - |
36 |
| - # Although dependencies will be installed automatically via the |
37 |
| - # library manager, your library under test may require an |
38 |
| - # unofficial version of a dependency. In those cases, the custom |
39 |
| - # libraries must be insalled prior to the test execution; those |
40 |
| - # installation commands should be placed in a shell script (that |
41 |
| - # will be executed by /bin/sh) and the shell script in your repo. |
42 |
| - # |
43 |
| - # Then, set this variable to the path to that file (relative to |
44 |
| - # the repository root) |
45 |
| - # |
46 |
| - # CUSTOM_INIT_SCRIPT: install_dependencies.sh |
0 commit comments