boklm pushed to branch main at The Tor Project / Applications / tor-browser-bundle-testsuite
Commits:
-
247eb051
by Nicolas Vigier at 2026-01-20T11:44:07+01:00
1 changed file:
Changes:
| ... | ... | @@ -113,15 +113,14 @@ targets: |
| 113 | 113 | |
| 114 | 114 | nightly:
|
| 115 | 115 | |
| 116 | - ### By default 'fetch' is set to 1 for nightly builds, meaning that new
|
|
| 117 | - ### commits will be fetched automatically during each build. You can
|
|
| 118 | - ### disable this during development if you want to do rebuilds to test
|
|
| 119 | - ### a specific change, but don't want rebuilds caused by unrelated
|
|
| 120 | - ### changes, or if you want to decide at which point new commits are
|
|
| 121 | - ### fetched. When 'fetch' is set to 'if_needed', new commits will only
|
|
| 122 | - ### be fetched if the selected commit (or branch, or tag) is not present,
|
|
| 123 | - ### which means that existing branches won't be updated. In that case
|
|
| 124 | - ### you can fetch new commits by running 'make fetch'.
|
|
| 125 | - fetch: 'if_needed'
|
|
| 116 | + ### By default 'fetch' is set to 'if_needed', meaning that new
|
|
| 117 | + ### commits will be fetched automatically during each build, if
|
|
| 118 | + ### the selected commit (or branch, or tag) is not present, or if
|
|
| 119 | + ### it is pointing to a branch. With the nightly target, some projects
|
|
| 120 | + ### are pointing to a branch, meaning they will be fetched for each
|
|
| 121 | + ### build. If you want to disable automatic fetchs and decide at
|
|
| 122 | + ### which point new commits are fetched, you can set 'fetch' to '0'
|
|
| 123 | + ### and run `make fetch` when you want to fetch new commits.
|
|
| 124 | + fetch: 0
|
|
| 126 | 125 | |
| 127 | 126 | # vim: filetype=yaml sw=2 |