An error occurred fetching the project authors.
- 20 Jul, 2016 1 commit
-
-
Robert Schilling authored
-
- 12 Jul, 2016 9 commits
-
-
tiagonbotelho authored
-
tiagonbotelho authored
changes the usage of simpleprojectdetails to already implemented basicprojectsdetails and changes the url to a more reader friendly format
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
changes the usage of simpleprojectdetails to already implemented basicprojectsdetails and changes the url to a more reader friendly format
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 11 Jul, 2016 1 commit
-
-
tiagonbotelho authored
-
- 08 Jul, 2016 1 commit
-
-
tiagonbotelho authored
changes the usage of simpleprojectdetails to already implemented basicprojectsdetails and changes the url to a more reader friendly format
-
- 06 Jul, 2016 2 commits
-
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 01 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 10 May, 2016 1 commit
-
-
Sean McGivern authored
`User#starred_projects` doesn't perform any visibility checks. This has a couple of problems: 1. It assumes a user can always view all of their starred projects in perpetuity (project not changed to private, access revoked, etc.). 2. It assumes that we'll only ever allow a user to star a project they can view. This is currently the case, but bugs happen. Add `User#viewable_starred_projects` to filter the starred projects by those the user either has explicit access to, or are public or internal. Then use that in all places where we list the user's starred projects.
-
- 09 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 29 Apr, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 13 Apr, 2016 3 commits
-
-
Robert Schilling authored
-
Robert Schilling authored
-
Robert Schilling authored
-
- 24 Mar, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
Also the specs have a minor improvement. Mainly the access right spec. Changes are reflected in the docs
-
- 23 Mar, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 13 Mar, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 04 Feb, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 29 Jan, 2016 1 commit
-
-
Josh Frye authored
-
- 11 Jan, 2016 1 commit
-
-
Tomasz Maczukin authored
-
- 07 Jan, 2016 2 commits
-
-
Douwe Maan authored
-
Tomasz Maczukin authored
-
- 05 Jan, 2016 1 commit
-
-
Tomasz Maczukin authored
-
- 03 Jan, 2016 1 commit
-
-
Stan Hu authored
Attempting to use the /projects/:id API by specifying :id in "namespace/project" format would always result in a 404 if the namespace contained a dot. The reason? From http://guides.rubyonrails.org/routing.html#specifying-constraints: "By default the :id parameter doesn't accept dots - this is because the dot is used as a separator for formatted routes. If you need to use a dot within an :id add a constraint which overrides this - for example id: /[^\/]+/ allows anything except a slash." Closes https://github.com/gitlabhq/gitlabhq/issues/9573
-
- 22 Dec, 2015 1 commit
-
-
Stan Hu authored
This standardizes all the project API formats. Also needed to support Huboard.
-
- 16 Dec, 2015 1 commit
-
-
Zeger-Jan van de Weg authored
Fixes #4112
-
- 11 Dec, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 06 Dec, 2015 1 commit
-
-
Stan Hu authored
Closes #3864
-
- 13 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
- Enable CI by default for all new projects
-
- 14 Oct, 2015 1 commit
-
-
Han Loong Liauw authored
Changed the authentication method for removing fork through API Reflected changes to new auth method in API specs
-