delta/gitlab/gitlab-ce.git/doc/user, branch fix-include-description-commit-message

Merge branch 'backport-time-tracking-ce' into 'master'

2017-01-19T09:50:56+00:00


Backport timetracking to CE

See merge request !8195

Merge branch '24915_merge_slash_command' into 'master'

2017-01-19T09:40:45+00:00


Support `/merge` slash command for MRs

Closes #24915

See merge request !7746

Treat environments matching `production/*` as Production

2017-01-09T15:35:24+00:00

For Cycle Analytics, the environment `production` is treated as a
special case, and used to update the `first_deployed_to_production_at`
metric.

With the Review Apps changes, slash syntax is used to group related
environments in the list. This is mostly used for `review/`
environments, but it's possible for people to have multiple production
environments, and someone might then want to group them like
`production/eu`, `production/us`, or even just make it look prettier
with `production/www.example.com`. In any of these cases, the first
deploy to one of these `production/*` environments now is treated as a
Production deploy.

Add images to issue creation from unresolved discussions

2016-12-22T21:54:08+00:00

[ci skip]

Add online terminal documentation

2016-12-19T21:27:08+00:00

Render math in Asciidoc and Markdown with KaTeX using code blocks

2016-12-14T16:50:54+00:00

Merge branch '23589-open-issue-for-mr' into 'master'

2016-12-06T14:04:14+00:00


Create an issue for all unresolved discussions in an MR

See merge request !7180

Merge branch 'glm-shorthand-reference' into 'master'

2016-12-06T12:17:12+00:00


GLM shorthand reference for projects from the same namespace

Closes #21679

See merge request !7255

Feature: delegate all open discussions to Issue

2016-12-05T19:55:45+00:00

When a merge request can only be merged when all discussions are
resolved. This feature allows to easily delegate those discussions to a
new issue, while marking them as resolved in the merge request.

The user is presented with a new issue, prepared with mentions of all
unresolved discussions, including the first unresolved note of the
discussion, time and link to the note.

When the issue is created, the discussions in the merge request will get
a system note directing the user to the newly created issue.

Merge branch 'fix/rename-mwbs-to-merge-when-pipeline-succeeds' into 'master'

2016-12-05T11:07:57+00:00


Rename MWBS service to Merge When Pipeline Succeeds

## What does this MR do?

This MR renames Merge When Build Succeeds feature to Merge When Pipeline Succeeds, because we recently changed the behavior, see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6675.

## Does this MR meet the acceptance criteria?

- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG.md) entry added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [x] All builds are passing

## What are the relevant issue numbers?

Closes #23354

See merge request !7135