An error occurred fetching the project authors.
- 23 Sep, 2013 1 commit
-
-
Izaak Alpert authored
GITLAB-1283 (GITLAB-869) Change-Id: I611e7e93f6292de08e1edc8d3ea77cf9087b6ded Conflicts: config/initializers/1_settings.rb
-
- 18 Jul, 2013 2 commits
-
-
Izaak Alpert authored
-Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
-
Izaak Alpert authored
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
-
- 12 Jul, 2013 1 commit
-
-
Angus MacArthur authored
Change-Id: Ib71ce8cf993627eada63d7d596fb302ec702f36e
-
- 08 Jul, 2013 1 commit
-
-
Angus MacArthur authored
Added ability to add and remove the forked from/to relatioinship between existing repos.
-
- 22 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 06 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 23 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 14 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 07 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 06 May, 2013 2 commits
-
-
Nihad Abbasov authored
-
Dmitriy Zaporozhets authored
-
- 02 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 01 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 10 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 01 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 25 Mar, 2013 1 commit
-
-
Andrew8xx8 authored
-
- 05 Mar, 2013 2 commits
-
-
Matt Humphrey authored
-
Angus MacArthur authored
-
- 27 Feb, 2013 3 commits
-
-
Sebastian Ziebell authored
Now the correct attribute is checked if it's available or not. Also fixed a test.
-
Sebastian Ziebell authored
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.
-
Sebastian Ziebell authored
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.
-
- 21 Feb, 2013 2 commits
-
-
Sebastian Ziebell authored
The API Documentation for project snippets got infos to return codes. Tests are added to check status codes when handling project snippets.
-
Sebastian Ziebell authored
-
- 20 Feb, 2013 2 commits
-
-
Matt Humphrey authored
-
Matt Humphrey authored
-
- 16 Feb, 2013 1 commit
-
-
Sebastian Ziebell authored
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.
-
- 14 Feb, 2013 4 commits
-
-
Sebastian Ziebell authored
-
Sebastian Ziebell authored
Status code 422 (Unprocessable Entity) returned if invalid url is given when creating or updating a project hook.
-
Sebastian Ziebell authored
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 authored
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 Feb, 2013 4 commits
-
-
Sebastian Ziebell authored
-
Sebastian Ziebell authored
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.
-
Sebastian Ziebell authored
-
Sebastian Ziebell authored
-
- 12 Feb, 2013 1 commit
-
-
Sebastian Ziebell authored
Different status codes in the API lib are returned on hook creation, update or deletion. If a required parameter is not given (e.g. `url` in `/projects/:id/hooks/:hook_id`) status code 400 (Bad request) is returned. On hook deletion a 200 status code is returned, regardless if the hook is present or not. This makes the DELETE function an idempotent operation. Appropriate tests are added to check these status codes.
-
- 08 Feb, 2013 4 commits
-
-
Sebastian Ziebell authored
-
Sebastian Ziebell authored
Accessing a repository branch that does not exist returns a 404 error instead of 200 now. Added a test.
-
Sebastian Ziebell authored
When adding a project hook a url must be specified or a 400 error code is returned * Specs added to check status code on handling project hooks * refactored code, extracted a method
-
Sebastian Ziebell authored
When a user is added to a project that is already a member of, a status code 201 is now returned to signal an idempotent operation. If something fails then instead of returning error code 404 different more specific error codes are returned. Status code 400 (Bad request) is returned when a required attribute, e.g. `access_level` is not given or 422 if there is a semantic error, e.g. should the `access_level` have an unsupported value. Specs are added to check these status codes.
-