14 Feb, 2013
1 commit
-
When reaching the project limit the API returns an error code 404 on the last possible project. The project itself is created and is available in the database (seems valid). A similar behavior can be observed when reaching the project limit via web client, but in this case the user is notified that the maximum number of projects is reached. The project itself is still created and can be accessed. Tests are added to check the behavior when reaching the project limit or one tries to exceed it via the API.
13 Feb, 2013
6 commits
-
…ew-unicorn-app-dir-fix Conflicts: config/unicorn.rb.example
-
Constants in Events looks good now
12 Feb, 2013
20 commits
-
Some fix for gitlab:gitlab_shell:check
-
Fixing issue #2970
-
Update lib/tasks/sidekiq.rake
-
API: Fixes return code when accessing non existent branch (#2922)
-
…nz/gitlabhq into hiroponz-easy-to-find-commit-on-network-graph
-
Disable autocomplete for admin/users form
-
Mac OS uses launchd instead of /etc/init.d to start daemons and tasks to be started by launchd MUST NOT daemon itself. So "nohup" here won't work for Mac OS. Can we add a "launchd" task to the rake file so that we can start sidekiq as "bundle exec rake sidekiq:launchd" ?
-
Gitlab incorrectly routes blobs to the compare controller depending on filename.
-
…into Undev-fix-db-after-updating-rails
11 Feb, 2013
13 commits
