forked from h5bp/html5-boilerplate
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.travis.yml
61 lines (50 loc) · 2.14 KB
/
.travis.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
# For more information about the configurations used
# in this file, please see the Travis CI documentation:
# http://docs.travis-ci.com
after_success:
# If the tests past, Travis will automatically download and execute
# the following script(s).
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# The `commit_build_changes.sh` script will run `npm run build`,
# and if that generates changes, it will commit them to the `master`
# branch:
#
# * ensuring that the content from the `dist/` directory is always
# in sync with the rest of the content
#
# * removing the need to execute the build step locally everytime
# a change is made (especially in the case of trivial changes
# such as typos)
#
# Note: The `commit_build_changes.sh` script will only run if the
# commit was made to the `master` branch.
- curl -sSL "https://raw.githubusercontent.com/h5bp-bot/scripts/0.5.0/commit_build_changes.sh" |
bash -s -- --branch "master"
--commit-message "Update content from the \`dist\` directory [skip ci]"
env:
global:
# The `secure` key contains three encrypted environment variables
# (GH_TOKEN, GH_USER_EMAIL and GH_USER_NAME), the values of which
# are used by the scripts that are automatically executed by Travis.
#
# Note: The `secure` key will only work for this repository, so if
# you create your own fork, you will need to generate your own key:
#
# travis encrypt -r "<username>/<repository>" \
# GH_TOKEN="<your_github_access_token>" \
# GH_USER_EMAIL="<your_email>" \
# GH_USER_NAME="<your_name>"
#
# To learn more about how to generate the:
#
# * `secure` key, see:
# http://docs.travis-ci.com/user/encryption-keys/
#
# * GitHub access token, see:
# https://help.github.com/articles/creating-an-access-token-for-command-line-use/
- secure: "mkLhS1ajE7gYNUdHsAfcW6vU9THb2DmPA01PQlXz2y/F3Ld0IwEpqrGGLWyg9ZSYr0g7xq+M46pPiZsfZgCYSLv0flA/RFLmiXcVQfap3BZf8sqTtE3M9AHuy9sxUgus2M9GA7Wupws2KC2PXZM0OT12GSSOCYQCLD3ySD4b4mE="
git:
depth: 10
language: node_js
node_js:
- "0.10"