BigW Consortium Gitlab

  1. 08 Nov, 2016 1 commit
  2. 07 Nov, 2016 2 commits
    • implements reset incoming email token on issues modal and account page, · 011e561b
      tiagonbotelho authored
      reactivates all tests and writes more tests for it
    • Rewritten spinach git_blame tests to rspec feature tests · e6e41478
      Lisanne Fellinger authored
      Fixing rubocop violations
      
      Relocated git_blame spec and fixed styling issue
      
      Rewritten spinach git_blame tests to rspec feature tests
      
      Fixing rubocop violations
      
      Relocated git_blame spec and fixed styling issue
      
      Rewritten spinach git_blame tests to rspec feature tests
      
      Fixing rubocop violations
      
      Rewritten spinach git_blame tests to rspec feature tests
      
      Fixing rubocop violations
      
      Rewritten spinach git_blame tests to rspec feature tests
      
      Fixing rubocop violations
      
      Relocated git_blame spec and fixed styling issue
  3. 06 Nov, 2016 1 commit
  4. 04 Nov, 2016 2 commits
  5. 03 Nov, 2016 1 commit
    • Show log corresponding to env in admin/logs · e900e53a
      Lukas Erlacher authored
      No matter which environment Gitlab was running as, the admin/logs view
      always showed production.log. This commit selects the logfile based
      on Rails.env.
      
      - Rename ProductionLogger to EnvironmentLogger
      - Make EnvironmentLogger logfile depend on env
      - Update spinach test for log tabs
  6. 01 Nov, 2016 2 commits
  7. 28 Oct, 2016 1 commit
  8. 26 Oct, 2016 1 commit
  9. 21 Oct, 2016 1 commit
    • Disable warming of the asset cache in Spinach tests under CI · cf31a0f0
      Stan Hu authored
      I suspect some combination of Knapsack tests cause no regular Rack tests
      to be loaded (i.e. all JavaScript tests), which leads to the error:
      
      ArgumentError: rack-test requires a rack application, but none was given
      
      In CI, we precompile all the assets so there is no need to warm the
      asset cache in any case.
      
      Closes #23613
  10. 20 Oct, 2016 1 commit
    • Differentiate the expire from leave event · 9124310f
      Callum Dryden authored
      At the moment we cannot see weather a user left a project due to their
      membership expiring of if they themselves opted to leave the project.
      This adds a new event type that allows us to make this differentiation.
      Note that is not really feasable to go back and reliably fix up the
      previous events. As a result the events for previous expire removals
      will remain the same however events of this nature going forward will be
      correctly represented.
  11. 19 Oct, 2016 1 commit
  12. 18 Oct, 2016 1 commit
  13. 17 Oct, 2016 5 commits
  14. 16 Oct, 2016 3 commits
  15. 15 Oct, 2016 2 commits
  16. 14 Oct, 2016 4 commits
  17. 06 Oct, 2016 2 commits
  18. 03 Oct, 2016 2 commits
  19. 27 Sep, 2016 2 commits
  20. 20 Sep, 2016 1 commit
  21. 18 Sep, 2016 1 commit
  22. 13 Sep, 2016 3 commits