06 Jun, 2013
2 commits
-
Authorize all teams to admin: fix 500 error on showing team page.
05 Jun, 2013
5 commits
-
Selectable deploy keys contain master projects
-
Created tests and refactored some code along the way Added stat graph util spec, refactored code finsihed up tests and refactors finsihed up tests and refactors
-
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
1 commit
-
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
03 Jun, 2013
1 commit
-
This refactors the `user_color_scheme_class` to use a hash with a default. This prevents problems with workers that don't have access to the current_user. Fixes issue #2758
01 Jun, 2013
1 commit
30 May, 2013
1 commit
27 May, 2013
2 commits
-
…itlabhq into dmedvinsky-add-defaults-create-group-team Conflicts: config/gitlab.yml.example
-
…rmer03-feature_teams_api Conflicts: doc/api/README.md
23 May, 2013
3 commits
21 May, 2013
1 commit
-
* Closing #3066 * Closing #3609
19 May, 2013
1 commit
16 May, 2013
3 commits
-
“Can create groups” and “Can create teams” had hardcoded defaults to `true`. Sometimes it is desirable to prohibit these for newly created users by default.
14 May, 2013
1 commit
08 May, 2013
3 commits
-
Add Gitlab::VersionInfo class to fix and simplify version check.
-
improve gfm autocomplete
-
It returns "yes" if required version is "1.7.10" and current version is "1.6.10", because the patch version of current version equals to that of required version.
07 May, 2013
3 commits
-
Code cleanup: Replace old hashes and remove trailing spaces
06 May, 2013
3 commits
05 May, 2013
3 commits
04 May, 2013
1 commit
-
update jquery-atwho-rails to v0.3.0 add autocomplete_source action to project for gfm autocomplete move init_autocomplete layout from head_panel to project_resource
03 May, 2013
1 commit
-
Internally public projects
02 May, 2013
4 commits
-
updated fork feature to use gitlab-shell for v5 of gitlab
-
When asking to fork a project and a project with the same name already exists (likely from a previous fork), the recovery from the fork failure would inadvertantly delete the repo of the existing destination project.
-
Takes into account 98bea4b1ff and 3b88636d3c.
-
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.
