delta/gitlab/gitlab-ce.git/spec, branch docs/markdown

Refactor issuables_counter_spec.

2016-11-16T08:44:49+00:00

Improve issuables_counter_spec relevance.

2016-11-16T08:44:49+00:00

Improve changes after MR review.

2016-11-16T08:44:49+00:00

Navigation bar issuables counters reflects dashboard issuables counters

2016-11-16T08:44:49+00:00

Merge branch '23584-triggering-builds-from-webhooks' into 'master'

2016-11-15T20:37:04+00:00


Add ref parameter for triggering builds with gitlab webhook from other project.

Currently GitLab can trigger builds from external tools like curl.
But there is no way to trigger builds with webhook from another GitLab project.
Executing webhook like `/projects/:id/trigger/builds?token=TOKEN&ref=master` results in such message from server:
```
400 No builds created
```

Problem is the ref from request body takes precedence of the ref from query string.
System tries to trigger build for nonexistent branch instead of `master`.
This is the feature of the Grape framework used to build GitLab api.

This MR adds optional `ref` parameter into the api url:
```
/projects/:id/ref/:ref/trigger/builds?token=TOKEN
```

This will lead that the ref in the url will have precedence of the ref inside request body.

This solution provides compatibility with current API urls.

Closes #23584

See merge request !7022

Merge branch 'grapify-groups-api' into 'master'

2016-11-15T14:28:33+00:00


Grapify the group API

## What are the relevant issue numbers?

Related to #22928

See merge request !7359

Add ref parameter for triggerring builds with gitlab webhook from other project.

2016-11-15T14:19:33+00:00

Merge branch 'grapify-merge-request-api' into 'master'

2016-11-15T13:44:31+00:00


Grapify the merge request API

Grapfiy the merge request API. I removed the test for checking if the source branch can be changed since this is an unused parameter. IMHO the test does not make sense.

## What are the relevant issue numbers?

Related to #22928

See merge request !7358

Grapify the group API

2016-11-15T13:36:42+00:00

Merge branch 'master-recursiveTree' into 'master'

2016-11-15T12:15:43+00:00


Issue #4270: Recursive option for files through API

## What does this MR do?
- Adds recursive param to tree API request. With this param we can get all repository paths in a single request. 
- Related [old github pull request](https://github.com/gitlabhq/gitlabhq/pull/9311)

## Are there points in the code the reviewer needs to double check?

## Why was this MR needed?
Requested in #4270 
## Screenshots (if relevant)

## Does this MR meet the acceptance criteria?

- [X] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [X] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [X] API support added
- Tests
  - [X] Added for this feature/bug
  - [x] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

## What are the relevant issue numbers?
Requested in #4270

See merge request !6088