An error occurred fetching the project authors.
- 11 Jan, 2019 1 commit
-
-
Shinya Maeda authored
We introduced releases_page feature flag. Given this feature is deemed stable, we should remove this flag before 19th.
-
- 10 Jan, 2019 1 commit
-
-
Francisco Javier López authored
-
- 08 Jan, 2019 1 commit
-
-
Stan Hu authored
As mentioned in https://gitlab.com/gitlab-org/gitlab-ee/issues/9035#note_129093444, Rails 5 switched ActionDispatch::Request so that it no longer inherits Rack::Request directly. A middleware that uses Rack::Request to read the environment may see stale request parameters if another middleware modifies the environment via ActionDispatch::Request. To be safe, we should be using ActionDispatch::Request everywhere.
-
- 07 Jan, 2019 7 commits
-
-
Steve Azzopardi authored
`project.latest_successful_builds_for(ref)` is being used to find a single job all the time. This results into us having to call `find_by` inside of the controller which violates our CodeReuse/ActiveRecord rubocop rule. Refactor `project.latest_successful_builds_for(ref)` to `project.latest_successful_build_for(job_name, ref)` which will execute the `find_by` inside of the model. Also create `project.latest_successful_build_for!(job_name, ref)` which raises an exception instead of returning nil.
-
Heinrich Lee Yu authored
Updated styling of export modal to use new CE SVG and CSS
-
Kamil Trzciński authored
This adds `project:, file:, ref:` specification support.
-
Stan Hu authored
As mentioned in https://gitlab.com/gitlab-org/gitlab-ee/issues/9035#note_129093444, Rails 5 switched ActionDispatch::Request so that it no longer inherits Rack::Request directly. A middleware that uses Rack::Request to read the environment may see stale request parameters if another middleware modifies the environment via ActionDispatch::Request. To be safe, we should be using ActionDispatch::Request everywhere.
-
Shinya Maeda authored
Add tests for the API and add a couple of tests Add revert revert
-
Shinya Maeda authored
Authorize against release not project
-
Heinrich Lee Yu authored
Also changes old calls to the service
-
- 04 Jan, 2019 6 commits
-
-
Mayra Cabrera authored
Adds the following initial CRUD endpoints for Clusters API: - GET list of clusters - GET specific cluster - POST add existing cluster (mimic of "Add cluster") - PUT update cluser - DELETE destroy cluster Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40473
-
Mayra Cabrera authored
Overrides: - optional_params_ee to set environment_scope - create_cluster_user_params: To add environment_scope
-
Grzegorz Bizon authored
-
Kamil Trzciński authored
Support asset links creation in `POST /projects/:id/release` See merge request gitlab-org/gitlab-ce!24056
-
Shinya Maeda authored
Fix coding style Improve coding style Decouple UPDATE and DELETE operations of asset links Rename links_attributes to assets:links Rename exposed param and updated spec
-
Shinya Maeda authored
- Add Releases::Links model - Expose it in release API - Add integration tests
-
- 03 Jan, 2019 3 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This commits adds a new class that is supposed to represent Grape API version, like `v3` or `v4`.
-
Grzegorz Bizon authored
-
- 02 Jan, 2019 2 commits
-
-
Mayra Cabrera authored
Adds the following initial CRUD endpoints for Clusters API: - GET list of clusters - GET specific cluster - POST add existing cluster (mimic of "Add cluster") - PUT update cluser - DELETE destroy cluster Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40473
-
Jonathon Reinhart authored
gitlab-org/gitlab-shell!166 added support for collecting push options from the environment, and passing them along to the /internal/post_receive API endpoint. This change handles the new push_options JSON element in the payload, and passes them on through to the GitPushService and GitTagPushService services. Futhermore, it adds support for the first push option, ci.skip. With this change, one can use 'git push -o ci.skip' to skip CI pipe execution. Note that the pipeline is still created, but in the "skipped" state, just like with the 'ci skip' commit message text. Implements #18667
-
- 31 Dec, 2018 8 commits
-
-
Jonathon Reinhart authored
gitlab-org/gitlab-shell!166 added support for collecting push options from the environment, and passing them along to the /internal/post_receive API endpoint. This change handles the new push_options JSON element in the payload, and passes them on through to the GitPushService and GitTagPushService services. Futhermore, it adds support for the first push option, ci.skip. With this change, one can use 'git push -o ci.skip' to skip CI pipe execution. Note that the pipeline is still created, but in the "skipped" state, just like with the 'ci skip' commit message text. Implements #18667
-
Francisco Javier López authored
-
Shinya Maeda authored
Add spec for all release API - GET, POST, PUT, DELETE. Also, fixes some minior bugs.
-
Shinya Maeda authored
Introduce DELETE endpoint in Release API
-
Alessio Caiazza authored
CreateReleaseService and UpdateReleaseService now takes all the release attributes as constructor parameters. This will simplify attribute expansion
-
Alessio Caiazza authored
-
Alessio Caiazza authored
-
Alessio Caiazza authored
This commit introduces Releases API under /api/v4/projects/:id/releases * We are introducing release policies at project level. * We are deprecating releases changes from tags, both api and web interface. * Tags::CreateService no longer create a release This feature is controlled by :releases_page feature flag
-
- 27 Dec, 2018 1 commit
-
-
Stan Hu authored
47d4890d changed the order of pagination so that the full list of branches would be passed to Gitaly to determine which ones had been merged, but this operation can timeout for large repositories with many branches. We only need to determine whether the found branches have been merged, so limit the scan to those. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55724
-
- 21 Dec, 2018 2 commits
-
-
Stan Hu authored
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 20 Dec, 2018 1 commit
-
-
Matija Čupić authored
-
- 19 Dec, 2018 4 commits
-
-
Jarka Košanová authored
- we now use the hierarchy class also for epics - also rename supports_nested_groups? into supports_nested_objects? - move it to a concern
-
Matija Čupić authored
-
Matija Čupić authored
-
Matija Čupić authored
-
- 17 Dec, 2018 1 commit
-
-
Bob Van Landuyt authored
We're filtering the events using `Event#visible_to_user?`. At most we're loading 100 events at once. Pagination is also dealt with in the finder, but the resulting array is wrapped in a `Kaminari.paginate_array` so the API's pagination helpers keep working. We're passing the total count into that paginatable array, which would include confidential events. But we're not disclosing anything.
-
- 16 Dec, 2018 2 commits
-
-
Jasper Maes authored
-
Jasper Maes authored
-