Andrew8xx8
b5db541338
All scopes must be in lambdas
2013-02-12 11:16:45 +04:00
Andrew8xx8
9a22ac63ec
Dynamic values must be in blocks if FG
2013-02-12 10:54:56 +04:00
Dmitriy Zaporozhets
d138b3de4b
Render events for team dashboard
2013-02-11 23:23:38 +02:00
Dmitriy Zaporozhets
06d9ccf484
Rails up to 3.2.12
2013-02-11 23:17:34 +02:00
Dmitriy Zaporozhets
68aa88c9bd
Fix project creation without import
2013-02-11 23:13:21 +02:00
Dmitriy Zaporozhets
8bf8c70c4b
Import repo feature
2013-02-11 23:00:12 +02:00
Dmitriy Zaporozhets
a699ebdbcc
handle attahcment with send_file
2013-02-11 21:31:19 +02:00
Dmitriy Zaporozhets
ab0cfc0036
fixing tests after refactoring
2013-02-11 20:28:27 +02:00
Dmitriy Zaporozhets
2a1fac9e4f
add import repo gitlab_shell call
2013-02-11 19:41:02 +02:00
Dmitriy Zaporozhets
ea0cb39d63
use proper name for gitlabshell worker
2013-02-11 19:27:26 +02:00
Dmitriy Zaporozhets
dd8d0a659d
Fix procfile and attachment in event nore
2013-02-11 19:25:06 +02:00
Dmitriy Zaporozhets
d64090b8a9
No gitolite in project any more
2013-02-11 19:16:59 +02:00
Dmitriy Zaporozhets
8e0b58d7e7
render note with attachment for event
2013-02-11 15:47:01 +02:00
Miguel Cabeça
f6957f7658
Fix image url for emoji.
2013-02-11 12:22:06 +00:00
Marin Jankovski
483f720861
UPdate field name.
2013-02-11 13:12:41 +01:00
Marin Jankovski
f339af858b
Test the delete acount option.
2013-02-11 13:06:37 +01:00
Dmitriy Zaporozhets
ab19196391
fix attachment uploader for aws
2013-02-11 10:14:32 +02:00
Dmitriy Zaporozhets
2d83e43db0
FIx gitlab:env:info
2013-02-11 10:02:52 +02:00
Dmitriy Zaporozhets
7a88bf0978
Fix gitlab:check
2013-02-11 09:58:02 +02:00
Dmitriy Zaporozhets
fcfb6d8438
Since gitlab-shell no sense to check hooks
2013-02-11 09:15:42 +02:00
Sebastian Ziebell
2bd955961c
Changed function to not_found.
...
Instead of using funtion `error!` the function `not_found!` is used to return 404 error. Adjusted documentation accordingly.
2013-02-09 21:01:17 +01:00
Dmitriy Zaporozhets
a404c43805
removing outdated checks
2013-02-09 15:34:04 +02:00
Dmitriy Zaporozhets
38737079b6
ignore docs by git
2013-02-09 15:26:47 +02:00
Dmitriy Zaporozhets
2f019b2b4c
cleanup rake tasks since no gitolite required
2013-02-09 15:21:19 +02:00
Dmitriy Zaporozhets
ff76e05271
show project head for empty project
2013-02-09 15:16:33 +02:00
Dmitriy Zaporozhets
38985390b0
Refactored and fixed seeds to work with gitlab-shell
2013-02-09 15:13:56 +02:00
Dmitriy Zaporozhets
152f87864c
remove useless warning
2013-02-09 12:32:24 +02:00
Dmitriy Zaporozhets
433f2dbcef
task to build missing projects with gitlab-shell
2013-02-09 12:30:49 +02:00
Sebastian Ziebell
56b3223945
Fixes test that checks status code of hook creation
2013-02-08 18:19:59 +01:00
Sebastian Ziebell
40e7846f3e
Status code 404 returned when retrieving non existent branch (issue #2922 )
...
Accessing a repository branch that does not exist returns a 404 error instead
of 200 now. Added a test.
2013-02-08 17:04:08 +01:00
Sebastian Ziebell
9544f90389
Adding a project hook returns status code 400 if url is not given
...
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
2013-02-08 16:48:05 +01:00
Sebastian Ziebell
818caf0b5d
API: refined status code handling when adding or updating a project member
...
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.
2013-02-08 14:33:29 +01:00
Sebastian Ziebell
8045a81bcf
Merge branch 'master' into fixes/api
2013-02-08 10:32:42 +01:00
Dmitriy Zaporozhets
2f0a75ab77
GitLab meta to 5.0
2013-02-08 08:55:39 +02:00
Dmitriy Zaporozhets
4b58030207
Merge pull request #2936 from jameswritescode/fix_installation_doc_typo
...
fix the gitlab-shell clone url in master installation doc
2013-02-07 22:41:19 -08:00
James Newton
d4c24b990f
fix the gitlab-shell clone url
2013-02-07 11:53:37 -06:00
Dmitriy Zaporozhets
66121d6caa
Improve devise views
2013-02-07 13:20:33 +02:00
Dmitriy Zaporozhets
210e9cd489
It should be 5.0.0pre
2013-02-07 13:05:30 +02:00
Dmitriy Zaporozhets
4e1757bfda
Merge branch 'gitlab-shell' of dev.gitlabhq.com:gitlab/gitlabhq
2013-02-07 08:26:39 +00:00
Dmitriy Zaporozhets
d09d87e3b0
fix deploy key spec
2013-02-07 10:25:47 +02:00
Dmitriy Zaporozhets
cdcf69d0d9
gitlab;shell init script
2013-02-07 10:06:39 +02:00
Dmitriy Zaporozhets
8ae1d812dc
deploy keys support for gitlab-shell api
2013-02-07 09:56:13 +02:00
Dmitriy Zaporozhets
48628d31d5
dont allow duplicates in ssh keys
2013-02-07 09:42:22 +02:00
Sebastian Ziebell
5d8a99f104
Test to check a user must be part of the team to see project.
...
A user must be part of the team to see a protected project. A test is given
to check that a 404 error is returned if the user can not see the project.
2013-02-06 17:11:01 +01:00
Sebastian Ziebell
a534c9b72d
A few fixes in documentation to notes, updates infos on status codes
...
A few fixes in the notes URI pattern (`notes` instead of `:notes`), also updated
the information to status codes. If `body` attribute is missing from a POST request
a status code 400 (Bad request) is returned. This reflects the code changes from
the previous commit.
2013-02-06 17:11:00 +01:00
Sebastian Ziebell
bb24275f8d
Status code 400 is returned if body is missing on note creation.
...
If a note is created with a POST request via API (`/projects/:id/notes`) status
code 400 is returned instead of 404. The resource itself exists but the request
is incomplete. Specs added to check different status codes when accessing, creating
and updating notes.
2013-02-06 17:11:00 +01:00
Sebastian Ziebell
b9d40d2524
Tests added to check status codes when handling milestone via API
...
A few more tests added to check status code when creating or updating milestones.
2013-02-06 17:11:00 +01:00
Sebastian Ziebell
5be0265fe7
Status code 400 returned if title not given in a milestone (via API)
...
If a milestone is created via API but no title given then status code 400 (Bad request)
is returned instead of 404. A small helper method handles the errors collection of a
milestone.
2013-02-06 17:10:29 +01:00
Sebastian Ziebell
41e93bbfe2
Test added to check creation of note to a non-existent MR via API
2013-02-06 17:05:55 +01:00
Sebastian Ziebell
f978a71f41
Creating MR comment without a note returns status code 400 (Bad request)
...
Creating a comment to an existing merge request via API without providing a note
returns a status code 400 now, suggesting a bad request. The reason for this
is the resource itself (MR) exists but the required property is not set.
2013-02-06 17:02:30 +01:00
