| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
Return comments in created order in merge request API
Closes #1832
See merge request !985
|
| |
| |
| |
| | |
Closes #1832
|
| |
| |
| |
| | |
the repository expire_cache method
|
| |
| |
| |
| | |
Closes #1362
|
| | |
|
|/
|
|
| |
in gitlab ci service.
|
|\
| |
| |
| |
| |
| |
| |
| | |
Filter by issues/merge requests without a milestone
Closes internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2372
See merge request !886
|
| |
| |
| |
| |
| | |
These specs also failed when run by themselves before this change, so
we've likely got some kind of cross-test contamination going on.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
API to set application settings for admin
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
See merge request !934
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|/ |
|
|
|
|
| |
Closes https://github.com/gitlabhq/gitlabhq/issues/9391
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
spec/features/issues_spec.rb
spec/models/forked_project_link_spec.rb
spec/models/hooks/service_hook_spec.rb
spec/models/hooks/web_hook_spec.rb
spec/models/project_services/hipchat_service_spec.rb
spec/requests/api/project_members_spec.rb
spec/requests/api/projects_spec.rb
spec/requests/api/system_hooks_spec.rb
spec/services/archive_repository_service_spec.rb
spec/support/matchers.rb
spec/tasks/gitlab/backup_rake_spec.rb
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
features/steps/project/merge_requests.rb
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | | |
Both work, but now we're consistent across the entire app.
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
These fixes were performed automatically by Rubocop's `-a` flag.
|
|/
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Order commit comments in API chronologically
When fetching commit comments via API, the comments were not ordered,
but just returned in the order Postgresql finds them. Now the API always
returns comments in chronological order.
Same as !628 but with CI
See merge request !768
|
| |
| |
| |
| |
| |
| | |
When fetching commit comments via API, the comments were not ordered,
but just returned in the order Postgresql finds them. Now the API always
returns comments in chronological order.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make namespace API available to all users
### What does this MR do?
This MR makes it possible for a user to query namespaces to which he/she has access. Also, it adds documentation for the existing API.
### Why was this MR needed?
Even though the `groups` API exists, it might still be useful to have an endpoint that tells the namespace type (e.g. `user` vs. `group`), especially if a user has access to a number of different projects.
### What are the relevant issue numbers?
Closes https://github.com/gitlabhq/gitlabhq/issues/9328
See merge request !708
|
| | |
| | |
| | |
| | | |
Closes https://github.com/gitlabhq/gitlabhq/issues/9328
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
Adds a version requirement which it didn't have before, at 2.0.0. This
version has breaking API changes in that the namespace is now `FFaker`
instead of `Faker`.
|
| | |
|
|/ |
|
|\
| |
| |
| | |
jubianchi-api-iid
|
| | |
|
|\ \
| |/
|/| |
Fix #6417: users with group permission should be able to create groups via API
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix user API tests succeeding for the wrong reason
|
| | |
| | |
| | |
| | |
| | | |
The requests were missing multiple required attributes, while testing for single attribute missing.
Added test for checking username as required attribute.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
the API
Updated projects.md to show tag_list field when performing GETs
Updated projects_spec.rb to include check for tag_list key in project list
Added changes to the CHANGELOG
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Add new service classes to create and update project and personal
snippets. These classes are responsible for enforcing restricted
visibility settings for non-admin users.
|
| |
| |
| |
| |
| | |
Allow admins to use restricted visibility levels when creating or
updating projects.
|
|/
|
|
|
| |
Give more specific errors in API responses and web UI flash messages
when a file update fails.
|