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
- Clone latest release.
- Improve the Local copy instructions.
- Remove the clone specific point in history instructions.
- When security is a concern it's best to use a local copy since it's possible to produce a git hash collision.
If you're passing a token to the script's publish report functions then best security practices would be to use a static copy of the script so you can be sure of the commands the token is used with:
26
+
- Download the latest version of the script from https://github.com/per1234/arduino-ci-script/releases by clicking one of the **Source code** links.
27
+
- Unzip the downloaded file.
28
+
- Copy arduino-ci-script.sh to a convenient location.
29
+
- Include the script in your project by adding the following line to your build configuration file:
30
+
```yaml
12
31
- source arduino-ci-script.sh
13
32
```
14
-
- It's possible to leave the script hosted at this repository.
15
-
```bash
33
+
34
+
##### Remote source
35
+
It's possible to leave the script hosted at this repository:
36
+
```yaml
37
+
# Use the tip of the master branch of arduino-ci-script
- The above doesn't allow you control over the version and would not be a good idea for security reasons if you use the functions that take a GitHub token argument. You could use the script at a specific point in the commit history with something like this:
0 commit comments