diff options
author | Evan Read <eread@gitlab.com> | 2019-02-18 12:36:13 +0300 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-02-18 12:36:13 +0300 |
commit | 47fb1c5235236c8e28bfdc87b013419ae1d85dc8 (patch) | |
tree | 0152ff66b8da3b175ed3f499aa52b039571c30a6 /doc/user/project/repository/web_editor.md | |
parent | 951e89127661150cdc23b8806085934ffdc4640f (diff) |
Remove consecutive blank lines from markdown files
For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.
Diffstat (limited to 'doc/user/project/repository/web_editor.md')
-rw-r--r-- | doc/user/project/repository/web_editor.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/user/project/repository/web_editor.md b/doc/user/project/repository/web_editor.md index 57e8437697b..ce9d23bf911 100644 --- a/doc/user/project/repository/web_editor.md +++ b/doc/user/project/repository/web_editor.md @@ -112,7 +112,6 @@ screenshot above will yield a branch named Since GitLab 9.0, when you click the `New branch` in an empty repository project, GitLab automatically creates the master branch, commits a blank `README.md` file to it and creates and redirects you to a new branch based on the issue title. If your [project is already configured with a deployment service][project-services-doc] (e.g. Kubernetes), GitLab takes one step further and prompts you to set up [auto deploy][auto-deploy-doc] by helping you create a `.gitlab-ci.yml` file. - After the branch is created, you can edit files in the repository to fix the issue. When a merge request is created based on the newly created branch, the description field will automatically display the [issue closing pattern] |