Commit 81527d40 authored by Craig Norris's avatar Craig Norris

Merge branch 'docs-aqualls-yet-more-spells' into 'master'

Fix yet more spelling issues

See merge request gitlab-org/gitlab!45345
parents 8b161d60 947b1aed
...@@ -146,6 +146,7 @@ failsafe ...@@ -146,6 +146,7 @@ failsafe
Falco Falco
fastlane fastlane
favicon favicon
Figma
Filebeat Filebeat
Fio Fio
firewalled firewalled
...@@ -312,6 +313,7 @@ passwordless ...@@ -312,6 +313,7 @@ passwordless
Patroni Patroni
performant performant
PgBouncer PgBouncer
Phabricator
phaser phaser
phasers phasers
Pipfile Pipfile
...@@ -352,6 +354,7 @@ Python ...@@ -352,6 +354,7 @@ Python
Qualys Qualys
Rackspace Rackspace
Raspbian Raspbian
Rdoc
reachability reachability
rebase rebase
rebased rebased
...@@ -433,7 +436,10 @@ smartcard ...@@ -433,7 +436,10 @@ smartcard
smartcards smartcards
SMTP SMTP
Sobelow Sobelow
Solarized
Sourcegraph Sourcegraph
sparkline
sparklines
spidering spidering
Splunk Splunk
SpotBugs SpotBugs
...@@ -449,6 +455,8 @@ subfolder ...@@ -449,6 +455,8 @@ subfolder
subfolders subfolders
subgraph subgraph
subgraphs subgraphs
subkey
subkeys
sublicense sublicense
sublicensed sublicensed
sublicenses sublicenses
...@@ -468,6 +476,7 @@ subtrees ...@@ -468,6 +476,7 @@ subtrees
sudo sudo
syslog syslog
tcpdump tcpdump
Thanos
Tiller Tiller
timecop timecop
todos todos
...@@ -490,6 +499,7 @@ unarchived ...@@ -490,6 +499,7 @@ unarchived
unarchives unarchives
unarchiving unarchiving
unassign unassign
unassigning
unassigns unassigns
uncheck uncheck
unchecked unchecked
......
...@@ -82,7 +82,7 @@ We flag any significant differences between Redcarpet and CommonMark Markdown in ...@@ -82,7 +82,7 @@ We flag any significant differences between Redcarpet and CommonMark Markdown in
If you have a large volume of Markdown files, it can be tedious to determine If you have a large volume of Markdown files, it can be tedious to determine
if they display correctly or not. You can use the if they display correctly or not. You can use the
[diff_redcarpet_cmark](https://gitlab.com/digitalmoksha/diff_redcarpet_cmark) [`diff_redcarpet_cmark`](https://gitlab.com/digitalmoksha/diff_redcarpet_cmark)
tool (not an officially supported product) to generate a list of files and the tool (not an officially supported product) to generate a list of files and the
differences between how RedCarpet and CommonMark render the files. It gives differences between how RedCarpet and CommonMark render the files. It gives
an indication if anything needs to be changed - often nothing needs an indication if anything needs to be changed - often nothing needs
......
...@@ -67,7 +67,7 @@ Images follow this naming convention: ...@@ -67,7 +67,7 @@ Images follow this naming convention:
``` ```
If your project is `gitlab.example.com/mynamespace/myproject`, for example, If your project is `gitlab.example.com/mynamespace/myproject`, for example,
then your image must be named `gitlab.example.com/mynamespace/myproject/my-app` at a mimimum. then your image must be named `gitlab.example.com/mynamespace/myproject/my-app` at a minimum.
You can append additional names to the end of an image name, up to three levels deep. You can append additional names to the end of an image name, up to three levels deep.
......
...@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Monorepo package management workflows # Monorepo package management workflows
Oftentimes, one project or Git repository may contain multiple different Oftentimes, one project or Git repository may contain multiple different
subprojects or submodules that all get packaged and published individually. sub-projects or submodules that all get packaged and published individually.
## Publishing different packages to the parent project ## Publishing different packages to the parent project
...@@ -36,9 +36,9 @@ as well as `Foo`. ...@@ -36,9 +36,9 @@ as well as `Foo`.
Following the instructions in the Following the instructions in the
[GitLab NPM registry documentation](../npm_registry/index.md), [GitLab NPM registry documentation](../npm_registry/index.md),
publishing `MyProject` consists of modifying the `package.json` file with a publishing `MyProject` consists of modifying the `package.json` file with a
`publishConfig` section, as well as either modifying your local NPM config with `publishConfig` section, as well as either modifying your local NPM configuration with
CLI commands like `npm config set`, or saving a `.npmrc` file in the root of the CLI commands like `npm config set`, or saving a `.npmrc` file in the root of the
project specifying these config settings. project specifying these configuration settings.
If you follow the instructions you can publish `MyProject` by running If you follow the instructions you can publish `MyProject` by running
`npm publish` from the root directory. `npm publish` from the root directory.
...@@ -65,7 +65,7 @@ A package is associated with a project on GitLab, but the package does not ...@@ -65,7 +65,7 @@ A package is associated with a project on GitLab, but the package does not
need to be associated with the code in that project. Notice when configuring need to be associated with the code in that project. Notice when configuring
NPM or Maven, you only use the `Project ID` to set the registry URL that the NPM or Maven, you only use the `Project ID` to set the registry URL that the
package is to be uploaded to. If you set this to any project that you have package is to be uploaded to. If you set this to any project that you have
access to and update any other config similarly depending on the package type, access to and update any other configuration similarly depending on the package type,
your packages are published to that project. This means you can publish your packages are published to that project. This means you can publish
multiple packages to one project, even if their code does not exist in the same multiple packages to one project, even if their code does not exist in the same
place. See the [project registry workflow documentation](./project_registry.md) place. See the [project registry workflow documentation](./project_registry.md)
......
...@@ -399,7 +399,7 @@ Administrators can add members with a "minimal access" role to a parent group. S ...@@ -399,7 +399,7 @@ Administrators can add members with a "minimal access" role to a parent group. S
automatically have access to projects and subgroups underneath. To support such access, administrators must explicitly add these "minimal access" users to the specific subgroups/projects. automatically have access to projects and subgroups underneath. To support such access, administrators must explicitly add these "minimal access" users to the specific subgroups/projects.
Users with minimal access can list the group in the UI and through the API. However, they cannot see Users with minimal access can list the group in the UI and through the API. However, they cannot see
details such as projects or subgroups. They do not have access to the group's page or list any of itssubgroups or projects. details such as projects or subgroups. They do not have access to the group's page or list any of its subgroups or projects.
## Project features ## Project features
......
...@@ -84,7 +84,7 @@ The default syntax theme is White, and you can choose among 5 different themes: ...@@ -84,7 +84,7 @@ The default syntax theme is White, and you can choose among 5 different themes:
[Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2389) in 13.0, the theme [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2389) in 13.0, the theme
you choose also applies to the [Web IDE](../project/web_ide/index.md)'s code editor and [Snippets](../snippets.md). you choose also applies to the [Web IDE](../project/web_ide/index.md)'s code editor and [Snippets](../snippets.md).
The themes are available only in the Web IDE file editor, except for the [dark theme](https://gitlab.com/gitlab-org/gitlab/-/issues/209808) and The themes are available only in the Web IDE file editor, except for the [dark theme](https://gitlab.com/gitlab-org/gitlab/-/issues/209808) and
the [solarized dark theme](https://gitlab.com/gitlab-org/gitlab/-/issues/219228), the [Solarized dark theme](https://gitlab.com/gitlab-org/gitlab/-/issues/219228),
which apply to the entire Web IDE screen. which apply to the entire Web IDE screen.
## Behavior ## Behavior
...@@ -131,15 +131,9 @@ You can choose between 2 options: ...@@ -131,15 +131,9 @@ You can choose between 2 options:
### Project overview content ### Project overview content
The project overview content setting allows you to choose what content you want to The **Project overview content** setting allows you to choose what content you want to
see on a project’s home page. see on a project’s home page.
You can choose between 3 options:
- Files and Readme (default)
- Readme
- Activity
### Tab width ### Tab width
You can set the displayed width of tab characters across various parts of You can set the displayed width of tab characters across various parts of
......
...@@ -252,7 +252,7 @@ GitLab CI/CD build environment. ...@@ -252,7 +252,7 @@ GitLab CI/CD build environment.
| `KUBE_NAMESPACE` | The namespace associated with the project's deployment service account. In the format `<project_name>-<project_id>-<environment>`. For GitLab-managed clusters, a matching namespace is automatically created by GitLab in the cluster. If your cluster was created before GitLab 12.2, the default `KUBE_NAMESPACE` is set to `<project_name>-<project_id>`. | | `KUBE_NAMESPACE` | The namespace associated with the project's deployment service account. In the format `<project_name>-<project_id>-<environment>`. For GitLab-managed clusters, a matching namespace is automatically created by GitLab in the cluster. If your cluster was created before GitLab 12.2, the default `KUBE_NAMESPACE` is set to `<project_name>-<project_id>`. |
| `KUBE_CA_PEM_FILE` | Path to a file containing PEM data. Only present if a custom CA bundle was specified. | | `KUBE_CA_PEM_FILE` | Path to a file containing PEM data. Only present if a custom CA bundle was specified. |
| `KUBE_CA_PEM` | (**deprecated**) Raw PEM data. Only if a custom CA bundle was specified. | | `KUBE_CA_PEM` | (**deprecated**) Raw PEM data. Only if a custom CA bundle was specified. |
| `KUBECONFIG` | Path to a file containing `kubeconfig` for this deployment. CA bundle would be embedded if specified. This config also embeds the same token defined in `KUBE_TOKEN` so you likely will only need this variable. This variable name is also automatically picked up by `kubectl` so you won't actually need to reference it explicitly if using `kubectl`. | | `KUBECONFIG` | Path to a file containing `kubeconfig` for this deployment. CA bundle would be embedded if specified. This configuration also embeds the same token defined in `KUBE_TOKEN` so you likely will only need this variable. This variable name is also automatically picked up by `kubectl` so you won't actually need to reference it explicitly if using `kubectl`. |
| `KUBE_INGRESS_BASE_DOMAIN` | From GitLab 11.8, this variable can be used to set a domain per cluster. See [cluster domains](#base-domain) for more information. | | `KUBE_INGRESS_BASE_DOMAIN` | From GitLab 11.8, this variable can be used to set a domain per cluster. See [cluster domains](#base-domain) for more information. |
### Custom namespace ### Custom namespace
......
...@@ -789,7 +789,7 @@ or with other versions of Python. ...@@ -789,7 +789,7 @@ or with other versions of Python.
kubectl edit gateway knative-ingress-gateway --namespace knative-serving kubectl edit gateway knative-ingress-gateway --namespace knative-serving
``` ```
Update the gateway to include the following tls: section and configuration: Update the gateway to include the following `tls:` section and configuration:
```shell ```shell
tls: tls:
......
...@@ -58,9 +58,9 @@ relevant language. ...@@ -58,9 +58,9 @@ relevant language.
| Language | Implementation | | Language | Implementation |
|---|---| |---|---|
| Go | [sourcegraph/lsif-go](https://github.com/sourcegraph/lsif-go) | | Go | [`sourcegraph/lsif-go`](https://github.com/sourcegraph/lsif-go) |
| JavaScript | [sourcegraph/lsif-node](https://github.com/sourcegraph/lsif-node) | | JavaScript | [`sourcegraph/lsif-node`](https://github.com/sourcegraph/lsif-node) |
| TypeScript | [sourcegraph/lsif-node](https://github.com/sourcegraph/lsif-node) | | TypeScript | [`sourcegraph/lsif-node`](https://github.com/sourcegraph/lsif-node) |
View a complete list of [available LSIF indexers](https://lsif.dev/#implementations-server) on their website and View a complete list of [available LSIF indexers](https://lsif.dev/#implementations-server) on their website and
refer to their documentation to see how to generate an LSIF file for your specific language. refer to their documentation to see how to generate an LSIF file for your specific language.
...@@ -85,7 +85,7 @@ To display the Deploy Boards for a specific [environment](../../ci/environments/ ...@@ -85,7 +85,7 @@ To display the Deploy Boards for a specific [environment](../../ci/environments/
[`kubernetes`](https://docs.gitlab.com/runner/executors/kubernetes.html) executor. [`kubernetes`](https://docs.gitlab.com/runner/executors/kubernetes.html) executor.
1. Configure the [Kubernetes integration](clusters/index.md) in your project for the 1. Configure the [Kubernetes integration](clusters/index.md) in your project for the
cluster. The Kubernetes namespace is of particular note as you will need it cluster. The Kubernetes namespace is of particular note as you will need it
for your deployment scripts (exposed by the `KUBE_NAMESPACE` env variable). for your deployment scripts (exposed by the `KUBE_NAMESPACE` environment variable).
1. Ensure Kubernetes annotations of `app.gitlab.com/env: $CI_ENVIRONMENT_SLUG` 1. Ensure Kubernetes annotations of `app.gitlab.com/env: $CI_ENVIRONMENT_SLUG`
and `app.gitlab.com/app: $CI_PROJECT_PATH_SLUG` are applied to the and `app.gitlab.com/app: $CI_PROJECT_PATH_SLUG` are applied to the
deployments, replica sets, and pods, where `$CI_ENVIRONMENT_SLUG` and deployments, replica sets, and pods, where `$CI_ENVIRONMENT_SLUG` and
......
...@@ -69,7 +69,7 @@ brew install git-lfs ...@@ -69,7 +69,7 @@ brew install git-lfs
``` ```
Once installed, **open your local repository in a terminal window** and Once installed, **open your local repository in a terminal window** and
install Git LFS in your repo. If you're sure that LFS is already installed, install Git LFS in your repository. If you're sure that LFS is already installed,
you can skip this step. If you're unsure, re-installing it won't do any harm: you can skip this step. If you're unsure, re-installing it won't do any harm:
```shell ```shell
...@@ -159,7 +159,7 @@ command line interface, file locks can be created for any file. ...@@ -159,7 +159,7 @@ command line interface, file locks can be created for any file.
### View exclusively-locked files ### View exclusively-locked files
To list all the files locked with LFS locally, open a terminal window in your To list all the files locked with LFS locally, open a terminal window in your
repo and run: repository and run:
```shell ```shell
git lfs locks git lfs locks
...@@ -189,7 +189,7 @@ Suggested workflow for shared projects: ...@@ -189,7 +189,7 @@ Suggested workflow for shared projects:
1. Lock the file. 1. Lock the file.
1. Edit the file. 1. Edit the file.
1. Commit your changes. 1. Commit your changes.
1. Push to the repo. 1. Push to the repository.
1. Get your changes reviewed, approved, and merged. 1. Get your changes reviewed, approved, and merged.
1. Unlock the file. 1. Unlock the file.
......
...@@ -96,7 +96,7 @@ back to both GitLab and GitHub when completed. ...@@ -96,7 +96,7 @@ back to both GitLab and GitHub when completed.
The mirroring is pull-only by default, so you may create or update the file on The mirroring is pull-only by default, so you may create or update the file on
GitHub: GitHub:
![Edit gitlab-ci.yml file](img/gemnasium/edit_gitlab-ci.png) ![Edit YAML file](img/gemnasium/edit_gitlab-ci.png)
1. Once your file has been committed, a new pipeline will be automatically 1. Once your file has been committed, a new pipeline will be automatically
triggered if your file is valid: triggered if your file is valid:
......
...@@ -101,7 +101,7 @@ If you are using a self-managed GitLab instance or if you are importing from Git ...@@ -101,7 +101,7 @@ If you are using a self-managed GitLab instance or if you are importing from Git
1. From the top navigation bar, click **+** and select **New project**. 1. From the top navigation bar, click **+** and select **New project**.
1. Select the **Import project** tab and then select **GitHub**. 1. Select the **Import project** tab and then select **GitHub**.
1. Select the first button to **List your GitHub repositories**. You are redirected to a page on [GitHub](https://github.com) to authorize the GitLab application. 1. Select the first button to **List your GitHub repositories**. You are redirected to a page on [GitHub](https://github.com) to authorize the GitLab application.
1. Click **Authorize gitlabhq**. You are redirected back to GitLab's Import page and all of your GitHub repositories are listed. 1. Click **Authorize GitlabHQ**. You are redirected back to GitLab's Import page and all of your GitHub repositories are listed.
1. Continue on to [selecting which repositories to import](#selecting-which-repositories-to-import). 1. Continue on to [selecting which repositories to import](#selecting-which-repositories-to-import).
### Using a GitHub token ### Using a GitHub token
...@@ -119,7 +119,7 @@ If you are not using the GitHub integration, you can still perform an authorizat ...@@ -119,7 +119,7 @@ If you are not using the GitHub integration, you can still perform an authorizat
1. Go to <https://github.com/settings/tokens/new> 1. Go to <https://github.com/settings/tokens/new>
1. Enter a token description. 1. Enter a token description.
1. Select the repo scope. 1. Select the repository scope.
1. Click **Generate token**. 1. Click **Generate token**.
1. Copy the token hash. 1. Copy the token hash.
1. Go back to GitLab and provide the token to the GitHub importer. 1. Go back to GitLab and provide the token to the GitHub importer.
...@@ -136,10 +136,10 @@ your GitHub repositories are listed. ...@@ -136,10 +136,10 @@ your GitHub repositories are listed.
1. Select the **Import** button next to any number of repositories, or select **Import all repositories**. Additionally, 1. Select the **Import** button next to any number of repositories, or select **Import all repositories**. Additionally,
you can filter projects by name. If filter is applied, **Import all repositories** only imports matched repositories. you can filter projects by name. If filter is applied, **Import all repositories** only imports matched repositories.
1. The **Status** column shows the import status of each repository. You can choose to leave the page open and it will 1. The **Status** column shows the import status of each repository. You can choose to leave the page open and it will
update in realtime or you can return to it later. update in real-time or you can return to it later.
1. Once a repository has been imported, click its GitLab path to open its GitLab URL. 1. Once a repository has been imported, click its GitLab path to open its GitLab URL.
![Github importer page](img/import_projects_from_github_importer_v12_3.png) ![GitHub importer page](img/import_projects_from_github_importer_v12_3.png)
## Mirroring and pipeline status sharing ## Mirroring and pipeline status sharing
...@@ -149,7 +149,7 @@ your imported repository in sync with its GitHub copy. ...@@ -149,7 +149,7 @@ your imported repository in sync with its GitHub copy.
Additionally, you can configure GitLab to send pipeline status updates back GitHub with the Additionally, you can configure GitLab to send pipeline status updates back GitHub with the
[GitHub Project Integration](../integrations/github.md). **(PREMIUM)** [GitHub Project Integration](../integrations/github.md). **(PREMIUM)**
If you import your project using [CI/CD for external repo](../../../ci/ci_cd_for_external_repos/index.md), then both If you import your project using [CI/CD for external repository](../../../ci/ci_cd_for_external_repos/index.md), then both
of the above are automatically configured. **(PREMIUM)** of the above are automatically configured. **(PREMIUM)**
## Improving the speed of imports on self-managed instances ## Improving the speed of imports on self-managed instances
......
...@@ -18,7 +18,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -18,7 +18,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
1. [From Perforce](perforce.md) 1. [From Perforce](perforce.md)
1. [From SVN](svn.md) 1. [From SVN](svn.md)
1. [From TFVC](tfvc.md) 1. [From TFVC](tfvc.md)
1. [From repo by URL](repo_by_url.md) 1. [From repository by URL](repo_by_url.md)
1. [By uploading a manifest file (AOSP)](manifest.md) 1. [By uploading a manifest file (AOSP)](manifest.md)
1. [From Gemnasium](gemnasium.md) 1. [From Gemnasium](gemnasium.md)
1. [From Phabricator](phabricator.md) 1. [From Phabricator](phabricator.md)
...@@ -32,7 +32,7 @@ There is also the option of [connecting your external repository to get CI/CD be ...@@ -32,7 +32,7 @@ There is also the option of [connecting your external repository to get CI/CD be
## Migrating from self-managed GitLab to GitLab.com ## Migrating from self-managed GitLab to GitLab.com
If you only need to migrate Git repos, you can [import each project by URL](repo_by_url.md). Issues and merge requests can't be imported. If you only need to migrate Git repositories, you can [import each project by URL](repo_by_url.md). Issues and merge requests can't be imported.
If you want to retain all metadata like issues and merge requests, you can use If you want to retain all metadata like issues and merge requests, you can use
the [import/export feature](../settings/import_export.md) to export projects from self-managed GitLab and import those projects into GitLab.com. the [import/export feature](../settings/import_export.md) to export projects from self-managed GitLab and import those projects into GitLab.com.
......
...@@ -56,7 +56,7 @@ You can start the import with: ...@@ -56,7 +56,7 @@ You can start the import with:
1. From your GitLab dashboard click **New project** 1. From your GitLab dashboard click **New project**
1. Switch to the **Import project** tab 1. Switch to the **Import project** tab
1. Click on the **Manifest file** button 1. Click on the **Manifest file** button
1. Provide GitLab with a manifest xml file 1. Provide GitLab with a manifest XML file
1. Select a group you want to import to (you need to create a group first if you don't have one) 1. Select a group you want to import to (you need to create a group first if you don't have one)
1. Click **List available repositories**. At this point, you will be redirected 1. Click **List available repositories**. At this point, you will be redirected
to the import status page with projects list based on the manifest file. to the import status page with projects list based on the manifest file.
......
...@@ -20,7 +20,7 @@ Git: ...@@ -20,7 +20,7 @@ Git:
it creates an integration record in their proprietary database for every file it creates an integration record in their proprietary database for every file
in the branch, regardless how many were actually changed. Whereas Git was in the branch, regardless how many were actually changed. Whereas Git was
implemented with a different architecture so that a single SHA acts as a pointer implemented with a different architecture so that a single SHA acts as a pointer
to the state of the whole repo after the changes, making it very easy to branch. to the state of the whole repository after the changes, making it very easy to branch.
This is what made feature branching workflows so easy to adopt with Git. This is what made feature branching workflows so easy to adopt with Git.
1. Also, context switching between branches is much easier in Git. If your manager 1. Also, context switching between branches is much easier in Git. If your manager
said 'You need to stop work on that new feature and fix this security said 'You need to stop work on that new feature and fix this security
......
...@@ -5,7 +5,7 @@ group: Import ...@@ -5,7 +5,7 @@ group: Import
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
--- ---
# Import project from repo by URL # Import project from repository by URL
You can import your existing repositories by providing the Git URL: You can import your existing repositories by providing the Git URL:
...@@ -16,4 +16,4 @@ You can import your existing repositories by providing the Git URL: ...@@ -16,4 +16,4 @@ You can import your existing repositories by providing the Git URL:
1. Click **Create project** to begin the import process 1. Click **Create project** to begin the import process
1. Once complete, you will be redirected to your newly created project 1. Once complete, you will be redirected to your newly created project
![Import project by repo URL](img/import_projects_from_repo_url.png) ![Import project by repository URL](img/import_projects_from_repo_url.png)
...@@ -14,8 +14,8 @@ See the project homepage for further information: <https://gitlab.com/esr/irker> ...@@ -14,8 +14,8 @@ See the project homepage for further information: <https://gitlab.com/esr/irker>
## Needed setup ## Needed setup
You will first need an Irker daemon. You can download the Irker code from its You will first need an Irker daemon. You can download the Irker code
repository on <https://gitlab.com/esr/irker>: [from its repository](https://gitlab.com/esr/irker):
```shell ```shell
git clone https://gitlab.com/esr/irker.git git clone https://gitlab.com/esr/irker.git
...@@ -55,6 +55,6 @@ case, `Aorimn` is treated as a nick and no more as a channel name. ...@@ -55,6 +55,6 @@ case, `Aorimn` is treated as a nick and no more as a channel name.
Irker can also join password-protected channels. Users need to append Irker can also join password-protected channels. Users need to append
`?key=thesecretpassword` to the channel name. When using this feature remember to `?key=thesecretpassword` to the channel name. When using this feature remember to
**not** put the `#` sign in front of the channel name; failing to do so will **not** put the `#` sign in front of the channel name; failing to do so will
result on irker joining a channel literally named `#chan?key=password` henceforth result on Irker joining a channel literally named `#chan?key=password` henceforth
leaking the channel key through the `/whois` IRC command (depending on IRC server leaking the channel key through the `/whois` IRC command (depending on IRC server
configuration). This is due to a long standing irker bug. configuration). This is due to a long standing Irker bug.
...@@ -55,7 +55,7 @@ include: ...@@ -55,7 +55,7 @@ include:
``` ```
creates an `a11y` job in your CI/CD pipeline, runs creates an `a11y` job in your CI/CD pipeline, runs
Pa11y against the webpages defined in `a11y_urls`, and builds an HTML report for each. Pa11y against the web pages defined in `a11y_urls`, and builds an HTML report for each.
The report for each URL is saved as an artifact that can be [viewed directly in your browser](../../../ci/pipelines/job_artifacts.md#browsing-artifacts). The report for each URL is saved as an artifact that can be [viewed directly in your browser](../../../ci/pipelines/job_artifacts.md#browsing-artifacts).
......
...@@ -164,8 +164,8 @@ For example: ...@@ -164,8 +164,8 @@ For example:
1. Capture the dynamic URL and save it into a `.env` file, e.g. `echo "ENVIRONMENT_URL=$CI_ENVIRONMENT_URL" >> review.env`. 1. Capture the dynamic URL and save it into a `.env` file, e.g. `echo "ENVIRONMENT_URL=$CI_ENVIRONMENT_URL" >> review.env`.
1. Set the `.env` file to be a [job artifact](../../../ci/pipelines/job_artifacts.md#job-artifacts). 1. Set the `.env` file to be a [job artifact](../../../ci/pipelines/job_artifacts.md#job-artifacts).
1. In the `load_performance` job: 1. In the `load_performance` job:
1. Set it to depend on the review job, so it inherits the env file. 1. Set it to depend on the review job, so it inherits the environment file.
1. Set the `K6_DOCKER_OPTIONS` variable with the [Docker cli option for env files](https://docs.docker.com/engine/reference/commandline/run/#set-environment-variables--e---env---env-file), for example `--env-file review.env`. 1. Set the `K6_DOCKER_OPTIONS` variable with the [Docker CLI option for environment files](https://docs.docker.com/engine/reference/commandline/run/#set-environment-variables--e---env---env-file), for example `--env-file review.env`.
1. Configure the k6 test script to use the environment variable in it's steps. 1. Configure the k6 test script to use the environment variable in it's steps.
Your `.gitlab-ci.yml` file might be similar to: Your `.gitlab-ci.yml` file might be similar to:
......
...@@ -84,7 +84,7 @@ Click **Expand file** on any file to view the changes for that file. ...@@ -84,7 +84,7 @@ Click **Expand file** on any file to view the changes for that file.
> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-file-by-file-diff-navigation). > - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-file-by-file-diff-navigation).
For larger merge requests it might sometimes be useful to review single files at a time. To enable, For larger merge requests it might sometimes be useful to review single files at a time. To enable,
from your avatar on the top-right navbar, click **Settings**, and go to **Preferences** on the left from your avatar on the top-right navigation bar, click **Settings**, and go to **Preferences** on the left
sidebar. Scroll down to the **Behavior** section and select **Show one file at a time on merge request's Changes tab**. sidebar. Scroll down to the **Behavior** section and select **Show one file at a time on merge request's Changes tab**.
Click **Save changes** to apply. Click **Save changes** to apply.
......
...@@ -65,8 +65,8 @@ meaningful commit messages and: ...@@ -65,8 +65,8 @@ meaningful commit messages and:
## Enabling squash for a merge request ## Enabling squash for a merge request
Anyone who can create or edit a merge request can choose for it to be squashed Anyone who can create or edit a merge request can choose for it to be squashed
on the merge request form. Users can select or unselect the checkbox at the moment on the merge request form. Users can select or clear the check box when they
they are creating the merge request: create the merge request:
![Squash commits checkbox on edit form](img/squash_edit_form.png) ![Squash commits checkbox on edit form](img/squash_edit_form.png)
......
...@@ -30,6 +30,8 @@ to do it for you. ...@@ -30,6 +30,8 @@ to do it for you.
To help you out, we've gathered some instructions on how to do that To help you out, we've gathered some instructions on how to do that
for the most popular hosting services: for the most popular hosting services:
<!-- vale gitlab.Spelling = NO -->
- [Amazon](https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html) - [Amazon](https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html)
- [Bluehost](https://www.bluehost.com/help/article/dns-management-add-edit-or-delete-dns-entries) - [Bluehost](https://www.bluehost.com/help/article/dns-management-add-edit-or-delete-dns-entries)
- [Cloudflare](https://support.cloudflare.com/hc/en-us/articles/201720164-Creating-a-Cloudflare-account-and-adding-a-website) - [Cloudflare](https://support.cloudflare.com/hc/en-us/articles/201720164-Creating-a-Cloudflare-account-and-adding-a-website)
...@@ -41,6 +43,8 @@ for the most popular hosting services: ...@@ -41,6 +43,8 @@ for the most popular hosting services:
- [Media Temple](https://mediatemple.net/community/products/dv/204403794/how-can-i-change-the-dns-records-for-my-domain) - [Media Temple](https://mediatemple.net/community/products/dv/204403794/how-can-i-change-the-dns-records-for-my-domain)
- [Microsoft](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727018(v=technet.10)) - [Microsoft](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727018(v=technet.10))
<!-- vale gitlab.Spelling = YES -->
If your hosting service is not listed above, you can just try to If your hosting service is not listed above, you can just try to
search the web for `how to add dns record on <my hosting service>`. search the web for `how to add dns record on <my hosting service>`.
......
...@@ -2,4 +2,4 @@ ...@@ -2,4 +2,4 @@
redirect_to: 'pages_ci_cd_template.md' redirect_to: 'pages_ci_cd_template.md'
--- ---
This document was moved to [pages_ci_cd_template.md](pages_ci_cd_template.md). This document was moved to [another location](pages_ci_cd_template.md).
...@@ -53,4 +53,4 @@ You can take some **optional** further steps: ...@@ -53,4 +53,4 @@ You can take some **optional** further steps:
![Change repo's path](../img/change_path_v12_10.png) ![Change repo's path](../img/change_path_v12_10.png)
- Now go to your SSG's configuration file and change the [base URL](../getting_started_part_one.md#urls-and-baseurls) - Now go to your SSG's configuration file and change the [base URL](../getting_started_part_one.md#urls-and-baseurls)
from `"project-name"` to `""`. The project name setting varies by SSG and may not be in the config file. from `"project-name"` to `""`. The project name setting varies by SSG and may not be in the configuration file.
...@@ -86,7 +86,7 @@ according to the markup language. ...@@ -86,7 +86,7 @@ according to the markup language.
| [reStructuredText](https://docutils.sourceforge.io/rst.html) | `rst` | | [reStructuredText](https://docutils.sourceforge.io/rst.html) | `rst` |
| [AsciiDoc](../../asciidoc.md) | `adoc`, `ad`, `asciidoc` | | [AsciiDoc](../../asciidoc.md) | `adoc`, `ad`, `asciidoc` |
| [Textile](https://textile-lang.com/) | `textile` | | [Textile](https://textile-lang.com/) | `textile` |
| [rdoc](http://rdoc.sourceforge.net/doc/index.html) | `rdoc` | | [Rdoc](http://rdoc.sourceforge.net/doc/index.html) | `rdoc` |
| [Org mode](https://orgmode.org/) | `org` | | [Org mode](https://orgmode.org/) | `org` |
| [creole](http://www.wikicreole.org/) | `creole` | | [creole](http://www.wikicreole.org/) | `creole` |
| [MediaWiki](https://www.mediawiki.org/wiki/MediaWiki) | `wiki`, `mediawiki` | | [MediaWiki](https://www.mediawiki.org/wiki/MediaWiki) | `wiki`, `mediawiki` |
...@@ -234,7 +234,7 @@ lock your files to prevent any conflicting changes. ...@@ -234,7 +234,7 @@ lock your files to prevent any conflicting changes.
## Repository's API ## Repository's API
You can access your repos via [repository API](../../../api/repositories.md). You can access your repositories via [repository API](../../../api/repositories.md).
## Clone in Apple Xcode ## Clone in Apple Xcode
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment