@@ -43,22 +43,23 @@ at the actions configuration file, [one for testing a PR](./.github/workflows/te
43
43
44
44
### How are the site and docs deployed?
45
45
46
- After each CI execution that happens in the ` dev ` branch, the script [ build-site.sh] ( ./build-site.sh )
46
+ After each CI execution that happens in the ` trunk ` branch, the script [ build-site.sh] ( ./build-site.sh )
47
47
is executed for deployment. This script checks for the string ` [deploy site] ` in the commit message.
48
48
49
- If the commit message contains that string, and the commit is in ` dev ` , a
49
+ If the commit message contains that string, and the commit is in ` trunk ` , a
50
50
[ GitHub action] ( ./.github/workflows/deploy.yml ) is triggered to build and deploy the site.
51
51
The site and docs will be built, and the changes will be committed to the branch ` publish `
52
52
by the user [ Selenium-CI] ( https://github.com/selenium-ci/ ) .
53
53
54
- * What is important to take into account is that the source files for the site are in the ` dev `
54
+ * What is important to take into account is that the source files for the site are in the ` trunk `
55
55
branch, and the files that get deployed are pushed to the ` publish ` branch.*
56
56
57
57
The site is deployed using GitHub pages, and the configuration for this can be seen at the
58
58
repo [ settings] ( https://github.com/SeleniumHQ/seleniumhq.github.io/settings ) (if you are a maintainer
59
59
you should be able to access the link).
60
60
61
- The selenium.dev domain is managed at https://www.gandi.net/en , if you need access to it, reach out to
61
+ The selenium.
62
+ domain is managed at https://www.gandi.net/en , if you need access to it, reach out to
62
63
any of the [ PLC] ( https://www.selenium.dev/project/structure/#plc ) or [ TLC] ( https://www.selenium.dev/project/structure/#tlc )
63
64
members, who can help you with that.
64
65
0 commit comments