Skip to content

Automatic redirects result in broken links

The handbook has a number of links to http://doc.gitlab.com/... which are being redirected to https://doc.gitlab.com instead of https://docs.gitlab.com and returning 404 errors. Full list below:

positioning-faq/index.html.md
36:1. With GitLab Enterprise Edition you can use [Repository Mirroring](http://doc.gitlab.com/ee/workflow/repository_mirroring.html) to mirror your open source projects from GitHub.com to your on premises GitLab server. Alternatively, if you want to have a public mirror of your GitLab project, you can now do so effortlessly using mirroring. GitHub Enterprise does not have mirroring.
37:1. Open source projects have different needs than projects developed on-premises by organizations. GitLab was built specifically for use by organizations on-premises and so has more features specific to the enterprise such as 5 levels of [permissions](http://doc.gitlab.com/ee/permissions/permissions.html), and the ability to install on a variety of operating systems.
117:    - http://doc.gitlab.com/ce/workflow/importing/migrating_from_svn.html

git-page-update/index.html.md
27:1. Here's where you can find step-by-step guides on the [basics of working with Git and GitLab](http://doc.gitlab.com/ce/gitlab-basics/README.html). You'll need those later.
28:1. Create your [SSH Keys](http://doc.gitlab.com/ce/gitlab-basics/create-your-ssh-keys.html).
128:  8. [Create a merge request](http://doc.gitlab.com/ce/gitlab-basics/add-merge-request.html) in [GitLab.com](https://gitlab.com/) with the branch that you created with your picture.
139:  2. Download Git, following the [start using git documentation](http://doc.gitlab.com/ce/gitlab-basics/start-using-git.html). Don't forget to add your Git username and to set your email.
140:  3. Follow the steps to create and add your [SSH keys](http://doc.gitlab.com/ce/gitlab-basics/create-your-ssh-keys.html). Note: in some of these steps, your [shell](http://doc.gitlab.com/ce/gitlab-basics/start-using-git.html) will require you to add your GitLab.com username and password.
141:  4. Clone the www-gitlab-com project through your shell, following the [command line commands documentation](http://doc.gitlab.com/ce/gitlab-basics/command-line-commands.html).
143:  6. Find the picture that you’d like to add to our team page, change the picture's name to the following format: `yournameinlowercase.jpg` or `yournameinlowercase.png` (There should be no space between first and last names e.g. firstlast.jpg or firstlast.png) and then add it to the `source/images/team/` directory. Follow the "[how to add an image](http://doc.gitlab.com/ce/gitlab-basics/add-image.html)" steps. Ensure the picture size is around 400x400 (it must be square) and the format is JPEG or PNG. You can resize your picture using a photo editor like [GIMP](http://www.gimp.org/) (cross-platform) or online by searching for "image resize". Any picture that you provide will be made black-and-white automatically after you add it to the team page.
150:  13. [Create a Merge Request](http://doc.gitlab.com/ce/gitlab-basics/add-merge-request.html) in [GitLab.com](https://gitlab.com/) with the branch that you created. Assign it to People Ops for review (the recommended assignee would be the Talent Operations Specialist who helped you with onboarding).

product/single-application/index.html.md
86:the codebase instead](http://doc.gitlab.com/ce/project_services/project_services.html) of being external. This ensures the automated tests for all

create-directory/index.html.md
12:To create a directory in your project, you need to use your [shell](http://doc.gitlab.com/ce/gitlab-basics/basic-git-commands.html). You can learn how to [start using Git on the command line](http://doc.gitlab.com/ce/gitlab-basics/start-using-git.html) and the [command line basic commands](http://doc.gitlab.com/ce/gitlab-basics/command-line-commands.html) before reading this documentation.

sales-faq-from-prospects/index.html.md
18:  Documentation: http://doc.gitlab.com/ee/integration/elasticsearch.html
32:  Documentation: http://doc.gitlab.com/ee/markdown/markdown.html#code-and-syntax-highlighting
47:  Documentation: http://doc.gitlab.com/ee/workflow/groups.html#gitlab-groups
53:  Documentation: http://doc.gitlab.com/ee/public_access/public_access.html
78:  Documentation: http://doc.gitlab.com/ee/analytics/contribution_analytics.html
86:  Log system: http://doc.gitlab.com/ee/logs/logs.html
88:  Audit Events: http://doc.gitlab.com/ee/administration/audit_events.html
95:  A: The respective hardware requirements with regards to the amount of users and repositories are listed in the GitLab documentation: http://doc.gitlab.com/ee/install/requirements.html#hardware-requirements
121:  A: Depending on the installation method and the GitLab version, there are multiple update guides in the documentation: http://doc.gitlab.com/ee/update/README.html

marketing/index.html.md
323:  <a href="http://doc.gitlab.com/">

handbook-usage/index.html.md
64:1. The handbook is for things concerning (future) GitLab team members only. If something concerns users of GitLab, it should be documented in the [GitLab documentation](http://doc.gitlab.com/), the [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit), the [CONTRIBUTING file](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md) or the [PROCESS file](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md).

engineering/workflow/index.html.md
18:Products at GitLab are built using the [GitLab Flow](http://doc.gitlab.com/ee/workflow/gitlab_flow.html).