delta/gitlab/gitlab-ce.git/lib/api, branch backport-ee-js-groups-api

Backport Group API code that was added in EE only

2016-10-31T17:47:30+00:00

Signed-off-by: Rémy Coutable

Merge branch '22271-drone-tag-pipeline-build' into 'master'

2016-10-31T14:09:39+00:00


Fix lightweight tags not processed correctly by GitTagPushService

## What does this MR do?

Fix lightweight tags not processed correctly by GitTagPushService

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

No

## Why was this MR needed?

Lightweight tags were being processed incorrectly, causing tag triggers to receive wrong information and not function properly.

## Does this MR meet the acceptance criteria?

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

## What are the relevant issue numbers?


Closes #22271

See merge request !6532

Merge branch 'dz-internal-api-fullpath' into 'master'

2016-10-28T21:36:40+00:00


Make internal api work with full repo path and name

## What does this MR do?

Make internal api work with full repo path and name

## Why was this MR needed?

So we can pass full repository path on filesystem from gitlab-shell instead of extracted one. We need this for nested groups support where project is can be nested under several groups. 

## What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/2772

See merge request !7148

Fix lightweight tags not processed correctly by GitTagPushService

2016-10-28T16:53:18+00:00

When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing
to the sha of the tag to the sha of the commit the tag points to. The
problem is that only annotated tags have `object_sha`s, lightweight tags
don't (it's nil), so (only) in their case we still need to use
`tag.target`.

Refactor storage path extraction from full repo path

2016-10-28T12:55:55+00:00

Signed-off-by: Dmitriy Zaporozhets

API: Fix booleans not recognized as such when using the `to_boolean` helper

2016-10-27T16:21:09+00:00

Signed-off-by: Rémy Coutable

Make internal api work with full repo path instead of name

2016-10-27T13:54:48+00:00

Signed-off-by: Dmitriy Zaporozhets

Fixes various errors when adding deploy keys caused by not exiting the control flow.

2016-10-26T10:54:47+00:00

When adding a deploy key that already exists in the project the existing key would not be returned, resulting in an attempt to create a new one, which in turn caused a 500 error due to an ActiveRecord exception.

When adding a deploy key that exists within another project the key would be joined to the project, but would also attempt to create a new one, which resulted in a 400 error due to the key already existing.

Fixes #22741
Fixes #21754

Signed-off-by: Rémy Coutable

Merge branch 'grapify-tags' into 'master'

2016-10-26T10:27:30+00:00


Grapify tags API

## What does this MR do?

Add the Grape-DSL to the tags API.

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

The delete endpoint only has a description but no success entity because we don't have one. We only return the branch name as JSON. Should I do something else?

## What are the relevant issue numbers?

Related to #22928

See merge request !6860

Grapify tags API

2016-10-26T08:34:16+00:00