Fix markdown in various docs
Clean up issues that may cause the docs-lint test to fail, such as trailing whitespace, no EOF newline, blockquotes, etc
This commit is contained in:
parent
e348def82f
commit
513d3f5811
|
|
@ -179,7 +179,7 @@ to make sure your VM is configured to use a _static_ public IP address (i.e. not
|
|||
or you will have to reconfigure the DNS `A` record each time Azure reassigns your VM a new public IP
|
||||
address. Read [IP address types and allocation methods in Azure][Azure-IP-Address-Types] to learn more.
|
||||
|
||||
## Let's open some ports!
|
||||
## Let's open some ports
|
||||
|
||||
At this stage you should have a running and fully operational VM. However, none of the services on
|
||||
your VM (e.g. GitLab) will be publicly accessible via the internet until you have opened up the
|
||||
|
|
@ -333,6 +333,7 @@ If you're running Windows, you'll need to connect using [PuTTY] or an equivalent
|
|||
If you're running Linux or macOS, then you already have an SSH client installed.
|
||||
|
||||
> **Note:**
|
||||
>
|
||||
> - Remember that you will need to login with the username and password you specified
|
||||
> [when you created](#basics) your Azure VM
|
||||
> - If you need to reset your VM password, read
|
||||
|
|
|
|||
|
|
@ -2,10 +2,6 @@
|
|||
comments: false
|
||||
---
|
||||
|
||||
---
|
||||
title: University | Process
|
||||
---
|
||||
|
||||
# Suggesting improvements
|
||||
|
||||
If you would like to teach a class or participate or help in any way please
|
||||
|
|
|
|||
|
|
@ -23,8 +23,6 @@ type: reference
|
|||
as opposed to individual stable branches
|
||||
- Consider creating a tag for each version that gets deployed
|
||||
|
||||
## Production branch
|
||||
|
||||

|
||||
|
||||
## Release branch
|
||||
|
|
@ -36,8 +34,6 @@ type: reference
|
|||
- Cherry-pick critical bug fixes to stable branch for patch release
|
||||
- Never commit bug fixes directly to stable branch
|
||||
|
||||
## Release branch
|
||||
|
||||

|
||||
|
||||
## More details
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ comments: false
|
|||
- Adapts to nearly any workflow
|
||||
- Fast, reliable and stable file format
|
||||
|
||||
## Help!
|
||||
## Help
|
||||
|
||||
Use the tools at your disposal when you get stuck.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ type: reference
|
|||
- Adapts to nearly any workflow.
|
||||
- Fast, reliable and stable file format.
|
||||
|
||||
## Help!
|
||||
## Help
|
||||
|
||||
Use the tools at your disposal when you get stuck.
|
||||
|
||||
|
|
|
|||
|
|
@ -57,5 +57,5 @@ service in GitLab.
|
|||
If builds are not triggered, ensure you entered the right GitLab IP address in
|
||||
Bamboo under 'Trigger IP addresses'.
|
||||
|
||||
> **Note:**
|
||||
> - Starting with GitLab 8.14.0, builds are triggered on push events.
|
||||
NOTE: **Note:**
|
||||
Starting with GitLab 8.14.0, builds are triggered on push events.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ To set up the mock CI service server, respond to the following endpoints
|
|||
|
||||
- `commit_status`: `#{project.namespace.path}/#{project.path}/status/#{sha}.json`
|
||||
- Have your service return `200 { status: ['failed'|'canceled'|'running'|'pending'|'success'|'success-with-warnings'|'skipped'|'not_found'] }`
|
||||
- If the service returns a 404, it is interpreted as `pending`
|
||||
- If the service returns a 404, it is interpreted as `pending`
|
||||
- `build_page`: `#{project.namespace.path}/#{project.path}/status/#{sha}`
|
||||
- Just where the build is linked to, doesn't matter if implemented
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
|
||||
> **Note:**
|
||||
> Starting from GitLab 8.5:
|
||||
>
|
||||
> - the `repository` key is deprecated in favor of the `project` key
|
||||
> - the `project.ssh_url` key is deprecated in favor of the `project.git_ssh_url` key
|
||||
> - the `project.http_url` key is deprecated in favor of the `project.git_http_url` key
|
||||
|
|
@ -12,6 +13,7 @@
|
|||
>
|
||||
> **Note:**
|
||||
> Starting from GitLab 11.2:
|
||||
>
|
||||
> - The `description` field for issues, merge requests, comments, and wiki pages
|
||||
> is rewritten so that simple Markdown image references (like
|
||||
> ``) have their target URL changed to an absolute URL. See
|
||||
|
|
@ -98,11 +100,12 @@ Below are described the supported events.
|
|||
|
||||
Triggered when you push to the repository except when pushing tags.
|
||||
|
||||
> **Note:** When more than 20 commits are pushed at once, the `commits` webhook
|
||||
attribute will only contain the first 20 for performance reasons. Loading
|
||||
detailed commit data is expensive. Note that despite only 20 commits being
|
||||
present in the `commits` attribute, the `total_commits_count` attribute will
|
||||
contain the actual total.
|
||||
NOTE: **Note:**
|
||||
When more than 20 commits are pushed at once, the `commits` webhook
|
||||
attribute will only contain the first 20 for performance reasons. Loading
|
||||
detailed commit data is expensive. Note that despite only 20 commits being
|
||||
present in the `commits` attribute, the `total_commits_count` attribute will
|
||||
contain the actual total.
|
||||
|
||||
**Request header**:
|
||||
|
||||
|
|
|
|||
|
|
@ -4,8 +4,7 @@ type: reference, howto
|
|||
|
||||
# Allow collaboration on merge requests across forks
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/17395)
|
||||
in GitLab 10.6.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/17395) in GitLab 10.6.
|
||||
|
||||
When a user opens a merge request from a fork, they are given the option to allow
|
||||
upstream members to collaborate with them on the source branch. This allows
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
# GitLab Maven Repository **(PREMIUM)**
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5811) in
|
||||
[GitLab Premium](https://about.gitlab.com/pricing/) 11.3.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5811) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.3.
|
||||
|
||||
With the GitLab [Maven](https://maven.apache.org) Repository, every
|
||||
project can have its own space to store its Maven artifacts.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
# GitLab NPM Registry **(PREMIUM)**
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5934)
|
||||
in [GitLab Premium](https://about.gitlab.com/pricing/) 11.7.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5934) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.7.
|
||||
|
||||
With the GitLab NPM Registry, every
|
||||
project can have its own space to store NPM packages.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
# Advanced Syntax Search **(STARTER ONLY)**
|
||||
|
||||
> **Notes:**
|
||||
>
|
||||
> - Introduced in [GitLab Enterprise Starter][ee] 9.2
|
||||
> - This is the user documentation. To install and configure Elasticsearch,
|
||||
> visit the [administrator documentation](../../integration/elasticsearch.md).
|
||||
|
|
|
|||
Loading…
Reference in New Issue