Read about our upcoming Code of Conduct on this issue

  1. 02 Oct, 2019 1 commit
  2. 11 Sep, 2019 1 commit
  3. 29 Jul, 2019 1 commit
  4. 17 Jul, 2019 1 commit
  5. 01 Apr, 2019 1 commit
  6. 05 Oct, 2018 1 commit
  7. 04 Oct, 2018 1 commit
    • Robert Speicher's avatar
      Add ProjectFeature check for feature flag · f1b2e652401c
      Robert Speicher authored
      This will allow an explicitly-disabled feature flag to override a
      feature being available for a project.
      
      As an extreme example, we could quickly disable issues across all
      projects at runtime by running `Feature.disable(:issues)`.
      f1b2e652401c
  8. 25 Sep, 2018 1 commit
    • Valery Sizov's avatar
      Geo: sync disabled wikis. Stage 2 · 8ce3572c59aa
      Valery Sizov authored
      We started syncing all the wiki regardless of the fact it's disabled or
      not. We couldn't do that in one stage because of needing of smoth update
      and deprecating things. This is the second stage that finally removes
      unused columns in the geo_node_status table.
      8ce3572c59aa
  9. 24 Jul, 2018 1 commit
  10. 09 Jul, 2018 1 commit
  11. 22 Dec, 2017 1 commit
  12. 02 Aug, 2017 1 commit
  13. 16 Jun, 2017 1 commit
    • Yorick Peterse's avatar
      Refactor Project.with_feature_available_for_user · cfe62efd6b28
      Yorick Peterse authored
      This method used to use a UNION, which would lead to it performing the
      same query twice; producing less than ideal performance. Further, in
      certain cases ActiveRecord could get confused and mess up the variable
      bindings, though it's not clear how/why exactly this happens.
      
      Fortunately we can work around all of this by building some of the WHERE
      conditions manually, allowing us to use a simple OR statement to get all
      the data we want without any of the above problems.
      cfe62efd6b28
  14. 05 Feb, 2017 1 commit
  15. 26 Jan, 2017 1 commit
  16. 17 Oct, 2016 1 commit
  17. 01 Sep, 2016 1 commit