@@ -10,8 +10,8 @@ Documentation is automatically generated and pushed to the `gh-pages` branch con
10
10
The [ slicer-apidocs-builder] ( https://github.com/Slicer/slicer-apidocs-builder ) tool is used within a CircleCI
11
11
build to checkout Slicer source code, build doxygen documentation and publish generated html pages.
12
12
13
- Each time the ` master ` branch of https://github.com/Slicer/Slicer is updated or each time a new release tag
14
- is pushed, the generated documentation is either added to the ` master ` folder or added to a new folder
13
+ Each time the ` main ` branch of https://github.com/Slicer/Slicer is updated or each time a new release tag
14
+ is pushed, the generated documentation is either added to the ` main ` folder or added to a new folder
15
15
named after the release tag. Then the updated content is pushed to the ` gh-pages ` branch.
16
16
17
17
The simple GitHub post-receive web hook handler triggering a CircleCI build is
@@ -31,7 +31,7 @@ Last TravisCI Cron Job: [![Build Status][travis_img]][travis]
31
31
[ max_size ] : https://help.github.com/articles/what-is-my-disk-quota/
32
32
[ cronjob ] : https://docs.travis-ci.com/user/cron-jobs/
33
33
[ travis ] : https://travis-ci.org/Slicer/apidocs.slicer.org
34
- [ travis_img ] : https://travis-ci.org/Slicer/apidocs.slicer.org.svg?branch=master
34
+ [ travis_img ] : https://travis-ci.org/Slicer/apidocs.slicer.org.svg?branch=main
35
35
36
36
37
37
## Programmatically request updates of ` gh-pages ` branch using TravisCI API
@@ -61,6 +61,6 @@ GITHUB_TOKEN=<YOUR_GITHUB_TOKEN> ./trigger-travis-squash.sh squash
61
61
62
62
It is covered by the Slicer License:
63
63
64
- https://github.com/Slicer/apidocs.slicer.org/blob/master /License.txt
64
+ https://github.com/Slicer/apidocs.slicer.org/blob/main /License.txt
65
65
66
66
0 commit comments