1. 26 Feb, 2016 1 commit
    • Zeger-Jan van de Weg's avatar
      Branded login page also in CE · 9a2869ab
      Zeger-Jan van de Weg authored
      The only major difference with the EE version is the change from a light and dark logo to only a header logo
      The dark logo wasn't used anyway, so it seemed to make sense to me to rename the field to the actual function of it
      9a2869ab
  2. 23 Feb, 2016 1 commit
  3. 22 Feb, 2016 1 commit
  4. 20 Feb, 2016 10 commits
  5. 19 Feb, 2016 17 commits
  6. 18 Feb, 2016 5 commits
  7. 17 Feb, 2016 1 commit
  8. 11 Feb, 2016 1 commit
    • Kirill Zaitsev's avatar
      Add new data to project in push, issue, merge-request and note webhooks data · b123171d
      Kirill Zaitsev authored
      - Add `avatar_url`, `description`, `git_ssh_url`, `git_http_url`,
        `path_with_namespace` and `default_branch` in `project` in push, issue,
        merge-request and note webhooks data
      - Deprecate the `ssh_url` in favor of `git_ssh_url` and `http_url` in
        favor of `git_http_url` in `project` for push, issue, merge-request and
        note webhooks data
      - Deprecate the `repository` key in push, issue, merge-request and
        note webhooks data, use `project` instead
      b123171d
  9. 10 Feb, 2016 1 commit
  10. 09 Feb, 2016 2 commits
    • Rémy Coutable's avatar
      Validate email addresses using Devise.email_regexp · b34963bc
      Rémy Coutable authored
      Also:
      - Get rid of legacy :strict_mode
      - Get rid of custom :email validator
      - Add some shared examples to spec emails validation
      b34963bc
    • Yorick Peterse's avatar
      Smarter flushing of branch statistics caches · 2ce0d063
      Yorick Peterse authored
      Instead of flushing the behind/ahead counts for all branches upon every
      push we now only flush the cache of branches that actually need to have
      these statistics recalculated. There are now basically 2 scenarios and
      their effects:
      
      1. A user pushes a commit to the default branch, this results in the
         cache being flushed for all branches.
      2. A user pushes to a non default branch, this results in _only_ the
         cache for that branch being flushed.
      
      The existing code (Repository#expire_cache) remains backwards compatible
      with the previous behaviour, the new behaviour is only applied when a
      branch name is passed as an argument. This ensures that when for example
      a project is deleted the cache for all branches is flushed.
      2ce0d063