- 06 May, 2016 1 commit
-
-
Fabio Huser authored
The user API documentation and the actual implementation were out of sync, missing certain newly introduced fields and beeing inconsistent between certain API definitions. The documentation was changed according the actual latest implementation. Signed-off-by: Fabio Huser <fabio@fh1.ch>
-
- 06 Apr, 2016 1 commit
-
-
Robert Schilling authored
-
- 17 Mar, 2016 1 commit
-
-
Achilleas Pipinellis authored
[ci skip]
-
- 15 Mar, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 04 Mar, 2016 1 commit
-
-
evuez authored
Added fields are last_sign_in_at and confirmed_at. They are available for GET /users/ and GET /users/:id for admins. Closes #840
-
- 08 Jan, 2016 1 commit
-
-
Gabriel Mazetto authored
-
- 28 Dec, 2015 1 commit
-
-
Michi302 authored
-
- 24 Dec, 2015 1 commit
-
-
Stan Hu authored
Needed to support Huboard
-
- 03 Sep, 2015 2 commits
-
-
Artem V. Navrotskiy authored
-
Artem V. Navrotskiy authored
-
- 30 Jul, 2015 1 commit
-
-
Douwe Maan authored
-
- 29 Jul, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Jul, 2015 1 commit
-
-
Steve Norman authored
-
- 24 Jun, 2015 1 commit
-
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/9391
-
- 04 May, 2015 1 commit
-
-
Sven Selberg authored
-
- 21 Jan, 2015 2 commits
-
-
Loic Dachary authored
Add the error code returned in the headers as well as an example of the JSON informative message returned in the body. Signed-off-by: Loic Dachary <loic@dachary.org>
-
Loic Dachary authored
Signed-off-by: Loic Dachary <loic@dachary.org>
-
- 18 Nov, 2014 1 commit
-
-
Daniel Serodio authored
The keys resource includes a create_at attribute
-
- 03 Nov, 2014 1 commit
-
-
Matthew Monaco authored
-
- 02 Nov, 2014 1 commit
-
-
Liam Monahan authored
-
- 15 Aug, 2014 1 commit
-
-
James Brooks authored
-
- 25 Jun, 2014 2 commits
-
-
Ciro Santilli authored
- multiple blank lines before header - skip header level - colon at end of header - break very long lines - align definition like lists at marker - case typos - informal contractions
-
Ciro Santilli authored
-
- 13 Jun, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 03 Jun, 2014 1 commit
-
-
Ciro Santilli authored
-
- 27 May, 2014 1 commit
-
-
Marin Jankovski authored
-
- 18 Apr, 2014 1 commit
-
-
Timm Friebe authored
Complements POST operation added in gitlabhq/gitlabhq#3146 Implement DELETE /users/:uid/keys/:id for admin users Fix "Line is too long. [83/80]" Use single quotes as advised Use single quotes as advised Use single quotes as advised Fix missing space around { and } Fix typo in documentation Only catch ActiveRecord::RecordNotFound, let other exceptions propagate Raise a "404 Not found" if key to be deleted cannot be found As requested by @jvanbaarsen in https://github.com/gitlabhq/gitlabhq/pull/6781#discussion_r11735114 Remove tab Unconfigured vim on this box, grrrr./
-
- 05 Apr, 2014 1 commit
-
-
Johannes Schleifenbaum authored
Fixes: #5505
-
- 01 Apr, 2014 1 commit
-
-
dosire authored
-
- 18 Jan, 2014 1 commit
-
-
Jerome Dalbert authored
-
- 01 Oct, 2013 1 commit
-
-
Marin Jankovski authored
-
- 29 Sep, 2013 1 commit
-
-
Boyan Tabakov authored
Also, is_admin and can_create_group are exposed in the user information. Fixed attributes_for_keys to process properly keys with boolean values (since false.present? is false).
-
- 30 Aug, 2013 1 commit
-
-
Johannes Schleifenbaum authored
-
- 29 Jul, 2013 1 commit
-
-
Johannes Schleifenbaum authored
-
- 29 May, 2013 1 commit
-
-
Drew Blessing authored
The API docs incorrectly referenced a few attributes associated with users. The 'blocked' attribute has been replaced with 'state'. Also, 'dark_scheme' seems to no longer be available in the User model so it should be removed from the exposed attributes in the API User entity. Add color scheme ID to API User entity
-
- 16 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 19 Mar, 2013 1 commit
-
-
Alex Denisov authored
-
- 17 Mar, 2013 1 commit
-
-
Kevin Lyda authored
Most of these are comments but a few are strings for users. Might be an idea to run this from time to time: https://github.com/lyda/misspell-check It runs mostly clean now.
-
- 06 Mar, 2013 2 commits
-
-
Sebastian Ziebell authored
All the info to return codes from the API functions are available in the `README.md` file as suggested.
-
Angus MacArthur authored
-