Skip to content

Commit

Permalink
Update READMEs (quoting of branch/tag name settings)
Browse files Browse the repository at this point in the history
  • Loading branch information
ralphlange committed Jun 30, 2020
1 parent 0bf7d23 commit 87942a7
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -365,16 +365,16 @@ This will make all builds (not just for your module) verbose.
Update the submodule in `.ci` first, then change your CI configuration
(if needed) and commit both to your module. E.g., to update your Travis
setup to release 3.1.0 of ci-scripts:
setup to release 3.1.1 of ci-scripts:
```bash
cd .ci
git pull origin v3.1.0
git pull origin v3.1.1
cd -
git add .ci
# if needed:
edit .travis.yml # and/or AppVeyor/GitHub Actions configuration
git add .travis.yml
git commit -m "Update ci-scripts submodule to v3.1.0"
git commit -m "Update ci-scripts submodule to v3.1.1"
```
Check the example configuration files inside ci-scripts (and their
Expand Down
12 changes: 12 additions & 0 deletions github-actions/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,18 @@
5. Push your changes and click on the `Actions` tab of your GitHub repository
page to see your build results.

## Specifics

#### Quote Environment Variable Values

Variable settings distinguish between numerical and string values.
Better quote all branch and tag names. E.g.,
```yaml
env:
BASE: "7.0"
```
to avoid ci-scripts trying to `git clone` with `--branch 7`.

## Caches

GitHub Actions provides caching of dependencies.
Expand Down

0 comments on commit 87942a7

Please sign in to comment.