- 17 3月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 23 1月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
* project_with_code -> project * project -> ermpty_project Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 04 12月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 11月, 2013 1 次提交
-
-
由 Jason Hollingsworth 提交于
Added visibility_level icons to project view (rather than just text). Added public projects to search results. Added ability to restrict visibility levels standard users can set.
-
- 18 11月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 07 11月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 09 10月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 24 9月, 2013 1 次提交
-
-
由 Izaak Alpert 提交于
GITLAB-1283 (GITLAB-869) Change-Id: I611e7e93f6292de08e1edc8d3ea77cf9087b6ded Conflicts: config/initializers/1_settings.rb
-
- 18 7月, 2013 2 次提交
-
-
由 Izaak Alpert 提交于
-Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
-
由 Izaak Alpert 提交于
The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
-
- 13 7月, 2013 1 次提交
-
-
由 Angus MacArthur 提交于
Change-Id: Ib71ce8cf993627eada63d7d596fb302ec702f36e
-
- 09 7月, 2013 1 次提交
-
-
由 Angus MacArthur 提交于
Added ability to add and remove the forked from/to relatioinship between existing repos.
-
- 22 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 07 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 23 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 14 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 08 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 07 5月, 2013 1 次提交
-
-
由 Nihad Abbasov 提交于
-
- 06 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 02 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 01 5月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 11 4月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 02 4月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 25 3月, 2013 1 次提交
-
-
由 Andrew8xx8 提交于
-
- 06 3月, 2013 1 次提交
-
-
由 Matt Humphrey 提交于
-
- 05 3月, 2013 1 次提交
-
-
由 Angus MacArthur 提交于
-
- 28 2月, 2013 2 次提交
-
-
由 Sebastian Ziebell 提交于
Now the correct attribute is checked if it's available or not. Also fixed a test.
-
由 Sebastian Ziebell 提交于
Added a helper method to check if required parameters are given in an API call. Can be used to return a `400 Bad Request` return code if a required attribute is missing. Code clean up and fixed tests.
-
- 27 2月, 2013 1 次提交
-
-
由 Sebastian Ziebell 提交于
The API documentation of repository is updated and now contains infos to status codes. Code documentation is also adjusted for `GET /projects/:id/repository/commits` and includes infos to pagination attributes. Tests are updated.
-
- 22 2月, 2013 2 次提交
-
-
由 Sebastian Ziebell 提交于
The API Documentation for project snippets got infos to return codes. Tests are added to check status codes when handling project snippets.
-
由 Sebastian Ziebell 提交于
-
- 20 2月, 2013 2 次提交
-
-
由 Matt Humphrey 提交于
-
由 Matt Humphrey 提交于
-
- 16 2月, 2013 1 次提交
-
-
由 Sebastian Ziebell 提交于
When a user is not authorized to see the list of hooks for a project, he is still able to access the hooks separately. For example if access to `GET /projects/:id/hooks` fails and returns a `403 Unauthorized` error it is still possible to access a hook directly via `GET /projects/:id/hooks/:hook_id`. Fixes access, also added tests to check access and status codes of hooks.
-
- 15 2月, 2013 1 次提交
-
-
由 Sebastian Ziebell 提交于
-
- 14 2月, 2013 3 次提交
-
-
由 Sebastian Ziebell 提交于
Status code 422 (Unprocessable Entity) returned if invalid url is given when creating or updating a project hook.
-
由 Sebastian Ziebell 提交于
When the project limit is reached the user is not allowed to create new ones. Instead of error code 404 the status code 403 (Forbidden) is returned with error message via API.
-
由 Sebastian Ziebell 提交于
When reaching the project limit the API returns an error code 404 on the last possible project. The project itself is created and is available in the database (seems valid). A similar behavior can be observed when reaching the project limit via web client, but in this case the user is notified that the maximum number of projects is reached. The project itself is still created and can be accessed. Tests are added to check the behavior when reaching the project limit or one tries to exceed it via the API.
-
- 13 2月, 2013 2 次提交
-
-
由 Sebastian Ziebell 提交于
-
由 Sebastian Ziebell 提交于
When using project snippets via API the functions now provide status codes for different situations other then only returning 404 error. If required parameters are missing, e.g. `title` when creating a project snippet a 400 (Bad request) error is returned. The snippet delete function now is idempotent and returns a 200 (Ok) regardless if the snippet with the given id is available or not. Changing return codes of these functions has the advantage that the 404 error is used only for resources, which are not available. Tests added to check these status codes when handling project snippets.
-