| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|\
| |
| |
| |
| |
| | |
Slack integration
See merge request !1151
|
| | |
|
|/ |
|
|
|
|
|
| |
Enable linking to commits, merge requests, and issues in other projects
by prepending a namespaced project path to the reference.
|
|
|
|
| |
That introduce select field type for services options.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Razer6-feature/zen_for_gfm
Conflicts:
CHANGELOG
|
| | |
|
|\ \
| |/
|/|
| |
| |
| | |
Fail harder in the backup script
See merge request !1143
|
| |
| |
| |
| |
| | |
This change also shows the output of failed Git commands during the
backup.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
API: Add support for forking a project via the API
This adds an API call to create a fork of a project.
Such API "fork button" has been requested by feature requests summing up with 37 votes.
The GitLab user has flagged one of them as accepting merge/pull requests for this feature.
Motivation:
The ability to create a fork is missing in the API.
(The API currently only supports adding and removing the "forked" relationship between two existing projects)
This feature (create fork thru the API) feature has been requested via two feature requests:
15 votes, 13 comments: to be able to fork a project through the API
http://feedback.gitlab.com/forums/176466-general/suggestions/4125380-to-be-able-to-fork-a-project-through-the-api (it was marked as completed in error by referring to the much more special change which allows to add&delete fork information)
22 votes, 3 comments: add a "fork project" API call that acts like the "fork button"
http://feedback.gitlab.com/forums/176466-general/suggestions/5820264-add-a-fork-project-api-call-that-acts-like-the
The implementation is described in the text of the commit message (click on the "..." field to open it).
A comprehensive test suite is added as well: It covers all 5 success / failure modes:
1. Success case
2. Failure if authenticated user has no access the the project to be forked
3. Failure if the forked project already exists in the authenticated user's namespace
4. Failure if the forked project does not exist
5. Failure if not authenticated
Documentation for the new API call is added to the project help page: doc/api/projects.md
I have 2 additional merge requests in progress, one is based on this feature and extend it, the other is related to querying forks.
The merge request that would be directly related is based on a request written comment of one of the feature requests (that was independently also requested in a but entry):
The ability to fork a project (thru the API) to a given namespace, eg. a group, in one case, for trainings.
As this request does not change code, but only adds a new request API for creating forks, it does not have
the capability to break existing code, and as the test spec demonstrates, it works.
It allocates the API request POST /projects/fork/:id, the only other API path I'd have thought of would have been POST /projects/:id/fork but that path is already taken by the API for creating a new fork relationship between projects, so POST /projects/fork/:id is the remaining possibility that I could see.
See merge request !191
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change adds POST /projects/fork/:id to the API for forking
a project into the namespace of the authenticated user, like the
"create fork" link in the GUI does. It also calls the same code.
Failure and permission checks (except for conflict) are already
implemented and handled in ForkService and the API, so the added
code is simple and does not alter anything.
|
|/
|
|
|
| |
Conflicts:
CHANGELOG
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/jubianchi/gitlabhq into jubianchi-api/issues-filter-milestone
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
CHANGELOG
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
CHANGELOG
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Protect default branch by default
Fixes #1543
See merge request !1130
|
| |/ |
|
|/ |
|
|
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
The gem can be enabled and configured via environment variables.
|
|\
| |
| |
| |
| |
| |
| |
| | |
API MR ordering
Fixes #1477
See merge request !1076
|
| | |
|
|\ \
| |/
|/|
| |
| |
| | |
Use sockets to connect to Redis
See merge request !1088
|
| | |
|
|\ \
| | |
| | | |
Adding ability to configure webhook timeout via gitlab.yml
|
| |/ |
|
|/ |
|
| |
|
|
|
|
|
| |
added documentation for shibboleth omniauth provider
updated changelog
|
|
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|\
| |
| |
| |
| |
| | |
Wrap arguments for `[ -z` in double quotes
See merge request !1071
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|/
|
|
|
| |
Conflicts:
CHANGELOG
|
|
|
|
| |
Updated API for annotated tags. Added tests for API. Strip leading/trailing whitespace from message, if present. Update CHANGELOG.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
API: Filter issues by labels
While working on [laboard](https://gitlab.com/jubianchi/laboard) I had some issues with the API : I was not able to filter issues by labels so I had to write some logic to do it on my side.
I think it will be useful to have this feature supported by the Gitlab API.
I added the filtering logic on `/issues` and `/projects/:id/issues`.
The commits are not squashed but I'll do it once everything seems ok to you.
See merge request !169
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
cirosantilli-sha-link
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
CHANGELOG
|
| | |
|