1. 16.10.2020 1 коммит
  2. 25.09.2020 1 коммит
  3. 24.09.2020 1 коммит
  4. 08.06.2020 1 коммит
  5. 03.06.2020 1 коммит
  6. 15.04.2020 1 коммит
  7. 13.03.2020 1 коммит
  8. 06.03.2020 2 коммита
  9. 04.03.2020 1 коммит
  10. 02.03.2020 2 коммита
  11. 29.02.2020 1 коммит
  12. 19.02.2020 1 коммит
  13. 30.09.2019 1 коммит
  14. 12.08.2019 1 коммит
  15. 15.07.2019 1 коммит
  16. 08.07.2019 1 коммит
  17. 31.05.2019 3 коммита
    • Marcel Amirault's avatar
      46907090
    • Bob Van Landuyt's avatar
      Setup Phabricator import
      · a6929f88
      Bob Van Landuyt создал
      This sets up all the basics for importing Phabricator tasks into
      GitLab issues.
      
      To import all tasks from a Phabricator instance into GitLab, we'll
      import all of them into a new project that will have its repository
      disabled.
      
      The import is hooked into a regular ProjectImport setup, but similar
      to the GitHub parallel importer takes care of all the imports itself.
      
      In this iteration, we're importing each page of tasks in a separate
      sidekiq job.
      
      The first thing we do when requesting a new page of tasks is schedule
      the next page to be imported. But to avoid deadlocks, we only allow a
      single job per worker type to run at the same time.
      
      For now we're only importing basic Issue information, this should be
      extended to richer information.
      a6929f88
    • Bob Van Landuyt's avatar
      Setup Phabricator import
      · 589b2db0
      Bob Van Landuyt создал
      This sets up all the basics for importing Phabricator tasks into
      GitLab issues.
      
      To import all tasks from a Phabricator instance into GitLab, we'll
      import all of them into a new project that will have its repository
      disabled.
      
      The import is hooked into a regular ProjectImport setup, but similar
      to the GitHub parallel importer takes care of all the imports itself.
      
      In this iteration, we're importing each page of tasks in a separate
      sidekiq job.
      
      The first thing we do when requesting a new page of tasks is schedule
      the next page to be imported. But to avoid deadlocks, we only allow a
      single job per worker type to run at the same time.
      
      For now we're only importing basic Issue information, this should be
      extended to richer information.
      589b2db0
  18. 05.05.2019 2 коммита
  19. 16.04.2019 1 коммит
  20. 25.01.2019 1 коммит
  21. 01.11.2018 1 коммит
  22. 19.08.2018 1 коммит
  23. 16.08.2018 2 коммита
  24. 12.07.2018 1 коммит
  25. 11.07.2018 2 коммита
  26. 08.05.2018 1 коммит
  27. 07.03.2018 1 коммит
  28. 05.03.2018 2 коммита
  29. 24.10.2017 1 коммит
  30. 06.09.2017 3 коммита