10 Mar, 2014
1 commit
-
Group owners were not able to remove any users from their group if they were the only owner.
25 Feb, 2014
3 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Main purpose is move big amount of methods from user, group, project models and place filtering logic in one place. It also fixes 500 error on group page for PostgreSQL Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
20 Feb, 2014
1 commit
-
Fixed Group avatars to only display when user has read permissions to at least one project in the group.
12 Feb, 2014
1 commit
10 Feb, 2014
1 commit
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
24 Jan, 2014
1 commit
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
16 Dec, 2013
1 commit
-
features for archive projects abilities for archived project other abilities for archive projects only limit commits and merges for archived projects ability changed to prohibited actions on archived projects added spec and feature tests for archive projects changed search bar not to include archived projects
26 Nov, 2013
1 commit
-
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.
26 Sep, 2013
1 commit
-
Before we have only owner_id to determine group owner With multiple owners per group we should get rid of owner_id in group. So from now @group.owner will always be nil but @group.owners return an actual array of users who can admin this group
25 Sep, 2013
1 commit
-
* Hooks and team pages allowed only for masters/owners * Group page allowed for admin * Corrent authentication for Projects controller * Hide some project elements from visitor
24 Sep, 2013
2 commits
11 Sep, 2013
1 commit
27 Aug, 2013
1 commit
21 Jun, 2013
1 commit
18 Jun, 2013
3 commits
06 Jun, 2013
2 commits
-
Authorize all teams to admin: fix 500 error on showing team page.
05 Jun, 2013
1 commit
-
500 error was occured in the following steps: 1. user1 creates new team "team1". 2. Assign team1 to project1. 3. Sign in as admin. This admin is not a member of team1. 4. Open project1 team setting page (/project1/team). 5. Click "team1" link in "Assigned teams" area. 6. 500 error. Fixed this issue.
04 Jun, 2013
2 commits
-
Conflicts: Gemfile.lock app/models/ability.rb app/models/project.rb app/views/snippets/_form.html.haml db/schema.rb features/steps/shared/paths.rb spec/factories.rb spec/models/project_spec.rb
08 May, 2013
1 commit
03 May, 2013
1 commit
-
Internally public projects
02 May, 2013
2 commits
-
See https://github.com/gitlabhq/gitlabhq/pull/3597#discussion-diff-4014638
-
Public projects listed in the public section will be linked to the actual project's page. Public projects now give any user Guest permissions to the project, allowing them to download the code, read and create issues, and view anything else in the project's pages. Ample access tests have been added to the project_access_spec to verify correct permissions and behavior on public projects. - Visitors to the site who are not logged in still cannot view the project's pages. - Logged-in users visiting a public project where they are not a team member can create issues, but not snippets. They can view the projects code, issues, merge requests, etc, just as if they were a Guest member of the project. - Since this is a public project, the user is also granted :download_code permissions, a permission normally reserved for Reporters, since they can clone the repo anyways and browse commits and branches locally.
15 Apr, 2013
1 commit
25 Mar, 2013
3 commits
24 Mar, 2013
1 commit
27 Feb, 2013
1 commit
18 Feb, 2013
1 commit
25 Jan, 2013
1 commit
24 Jan, 2013
1 commit
21 Jan, 2013
1 commit
17 Jan, 2013
1 commit
