This is an initiative to ensure all documentation complies completely
with the Documentation Style Guide section "Documentation is the single
source of truth (SSOT)" according to this epic
https://gitlab.com/groups/gitlab-org/-/epics/1280.

In particular, the changes of this commit touch all files under
doc/install/. Most notably:

- install/redis.md:
        Redirect to Redis section of install guide.

- install/pivotal/index.md:
        Changed its content to reflect the current status, which is no
        longer supported (since 2017!).

- install/google-protobuf.md:
        Incorporated inside installation.md under the troubleshooting section.

- install/openshift_and_gitlab.md:
        Clarified that this guide is no longer relevant. We might want to
        redirect to the Chart docs in the future.

- install/structure.md:
        Incorporated inside installation.md under its own section.

- install/kubernetes/index.md:
        Redirected to https://docs.gitlab.com/charts

We can query namespaces, and nested projects.

Projects now exposes statistics

This extends POST#:id/repository/commits to allow the optional parameter
`:start_project`, which will allow targeting other projects besides the
one derived from `:id`.

Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/50850

Charlie Ablett authored 5 years ago and Charlie Ablett committed 5 years ago

- Comply doc with guidelines
- Improve tests for readability and completeness
- Separate out phases visually with newlines
- Add `format_message` test
- test readability
- code and test structure/styling
- static query analyzers
- call `as_json` on `provided_variables`
- add exception handling

This sets up all the basics for importing Phabricator tasks into
GitLab issues.

To import all tasks from a Phabricator instance into GitLab, we'll
import all of them into a new project that will have its repository
disabled.

The import is hooked into a regular ProjectImport setup, but similar
to the GitHub parallel importer takes care of all the imports itself.

In this iteration, we're importing each page of tasks in a separate
sidekiq job.

The first thing we do when requesting a new page of tasks is schedule
the next page to be imported. But to avoid deadlocks, we only allow a
single job per worker type to run at the same time.

For now we're only importing basic Issue information, this should be
extended to richer information.

Previously the documentation was separated.  If we want to bake
quality into the product, how better than to include everything
we use directly in the development documentation

Signed-off-by: ddavison <ddavison@gitlab.com>

Fix broken internal doc link

Move documentation for page objects to the e2e section

It used to be the case that GitLab created symlinks for each repository
to one copy of the Git hooks, so these ran when required. This changed
to set the hooks dynamically on Gitaly when invoking Git.

The side effect is that we didn't need all these symlinks anymore, which
Gitaly doesn't create anymore either. Now that means that the tests in
GitLab-Rails should test for it either.

Related: https://gitlab.com/gitlab-org/gitaly/issues/1392#note_175619926

Marcia Ramos authored 5 years ago and Achilleas Pipinellis committed 5 years ago

For ssot epic

Marcia Ramos authored 5 years ago and Achilleas Pipinellis committed 5 years ago

For CI services examples

Thiago Presa authored 5 years ago and Achilleas Pipinellis committed 5 years ago

The docs for the highest_role field was incorrectly added to the
/users endpoint. This commit adds it to the /users/:id

Achilleas Pipinellis authored 5 years ago and Evan Read committed 5 years ago

The following EE files had small differences with their CE counterpart
so they have been ported to CE:

- doc/api/boards.md
- doc/api/discussions.md
- doc/api/notes.md
- doc/api/resource_label_events.md
- doc/api/services.md

Jan Provaznik authored 5 years ago and Mayra Cabrera committed 5 years ago

It assures that requests are aborted after 60 seconds, otherwise
an exception is raised. This exception is logged by Sentry, also
there is a Prometheus counter for measuring number of requests in each
state.

Evan Read authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Ensures we give instructions for how to create ssh keys
in a single place only.

Sam Beckham authored 5 years ago and Achilleas Pipinellis committed 5 years ago

https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12805/

Improve existing FDW documentation in `doc/development` to include
additional information about the architecture and how to use FDW as
a developer.