You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!--
Have any questions? Check out the contributing docs at https://gatsby.app/contribute, or
ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->
## Description
<!-- Write a brief description of the changes introduced by this PR -->
## Related Issues
<!--
Link to the issue that is fixed by this PR (if there is one)
e.g. Fixes#1234, Addresses #1234, Related to #1234, etc.
-->
Copy file name to clipboardExpand all lines: docs/docs/deploying-to-gitlab-pages.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,6 @@ where the static files are kept. `only:` and `master` tells the CI to only run t
64
64
65
65
Add that configuration, and with the next master branch push, your site should have been built correctly. This can be checked by going to your repository on GitLab, and selecting CI/CD in the sidebar. This will then show you a log of all jobs that have either succeeded or failed. You can click on the failed status, and then select the job to get more information about why your build may have failed.
66
66
67
-
If all went well, you should now be able to access your site. It will be hosted under gitlab.io - for example if you have have a repository under your namespace, the url will be yourname.gitlab.io/examplerepository.
67
+
If all went well, you should now be able to access your site. It will be hosted under gitlab.io - for example if you have a repository under your namespace, the url will be yourname.gitlab.io/examplerepository.
68
68
69
69
Visit the [GitLab Pages](https://gitlab.com/help/user/project/pages/getting_started_part_one.md) to learn how to setup custom domains and find out about advanced configurations.
0 commit comments