01 Jun, 2013
1 commit
-
when there are large number of members of in a team, for me 260+ From: [2013-06-01 00:55:01] Rendered team_members/_team_member.html.haml (206.9ms) [2013-06-01 00:55:01] Rendered team_members/_team.html.haml (54479.2ms) To: [2013-06-02 02:40:36] Rendered team_members/_team_member.html.haml (2.1ms) [2013-06-02 02:40:36] Rendered team_members/_team.html.haml (1412.6ms)
31 May, 2013
2 commits
-
Fix rake gitlab:env:info command line in Issue tracker guidelines.
30 May, 2013
8 commits
29 May, 2013
17 commits
-
Style target notes for easy visual identification
-
Fix not displaying a slash after namespace.
-
Remove user directory path assumptions
-
Update api docs and remove old attribute from User entity.
-
Update suggestion for Check.rake
-
grammar fix in an error message (very minor change)
-
adding update info regarding gitlab-shell config.yml (re: dashboard update problems)
-
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
-
Jira - Fixed Jira Issue tracker support
28 May, 2013
7 commits
-
update pull request guidelines, allow for submitting of tests that expos...
27 May, 2013
5 commits
-
Jira issues numbering format are like: "PROJECT-1234". Changed the regular expression to support Jira issues linking, in addition to the normal #123. Added Jira Issue tracker configuration example
-
add code comment about backing up folder when restoring
