Skip to content
Snippets Groups Projects
  1. Feb 12, 2025
  2. Feb 10, 2025
    • GitLab Housekeeping Bot's avatar
      Regenerate RuboCop TODO files · f7c59ccd
      GitLab Housekeeping Bot authored
      Due to code changes, some RuboCop offenses get automatically fixed over time. To avoid reintroducing these
      offenses, we periodically regenerate the `.rubocop_todo` files.
      
      While reviewing this merge request make sure:
      
        1. The files are only added, renamed or removed from the todo lists or the comments are updated and there
           should be no other changes.
        2. **rubocop**, **haml-lint**, and **haml-lint** jobs pass.
      
      Read more about this [automation here](https://docs.gitlab.com/ee/development/rubocop_development_guide.html#periodically-generating-rubocop-todo-files).
      
      If you have any questions, feel free to reach out in the `#f_rubocop` channel on Slack.
      
      ### Responsibility of Assignee
      
      We pick a random ~backend reviewer as the assignee. You should make sure to fix any merge conflicts if they
      arise and get this merge request merged like any other merge request authored by you.
      
      ### Responsibility of Reviewer
      
      Since these changes are simple we skip the initial ~backend review for efficiency and request a review from a
      random ~backend maintainer to review and merge these changes.
      
      This change was generated by
      [gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
      using the Keeps::GenerateRubocopTodos keep.
      
      To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
      label ~"GitLab Housekeeper" and consider pinging the author of this keep.
      
      Changelog: other
      f7c59ccd
  3. Jan 31, 2025
  4. Jan 29, 2025
    • Auto-quarantining bot's avatar
      Regenerate RuboCop TODO files · fca2ade3
      Auto-quarantining bot authored
      Due to code changes, some RuboCop offenses get automatically fixed over time. To avoid reintroducing these
      offenses, we periodically regenerate the `.rubocop_todo` files.
      
      While reviewing this merge request make sure:
      
        1. The files are only added, renamed or removed from the todo lists or the comments are updated and there
           should be no other changes.
        2. **rubocop**, **haml-lint**, and **haml-lint** jobs pass.
      
      Read more about this [automation here](https://docs.gitlab.com/ee/development/rubocop_development_guide.html#periodically-generating-rubocop-todo-files).
      
      If you have any questions, feel free to reach out in the `#f_rubocop` channel on Slack.
      
      ### Responsibility of Assignee
      
      We pick a random ~backend reviewer as the assignee. You should make sure to fix any merge conflicts if they
      arise and get this merge request merged like any other merge request authored by you.
      
      ### Responsibility of Reviewer
      
      Since these changes are simple we skip the initial ~backend review for efficiency and request a review from a
      random ~backend maintainer to review and merge these changes.
      
      This change was generated by
      [gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
      using the Keeps::GenerateRubocopTodos keep.
      
      To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
      label ~"GitLab Housekeeper" and consider pinging the author of this keep.
      
      Changelog: other
      Verified
      fca2ade3
  5. Jan 17, 2025
  6. Jan 13, 2025
    • GitLab Housekeeping Bot's avatar
      Regenerate RuboCop TODO files · 845076c6
      GitLab Housekeeping Bot authored
      Due to code changes, some RuboCop offenses get automatically fixed over time. To avoid reintroducing these
      offenses, we periodically regenerate the `.rubocop_todo` files.
      
      While reviewing this merge request make sure:
      
        1. The files are only added, renamed or removed from the todo lists or the comments are updated and there
           should be no other changes.
        2. **rubocop**, **haml-lint**, and **haml-lint** jobs pass.
      
      Read more about this [automation here](https://docs.gitlab.com/ee/development/rubocop_development_guide.html#periodically-generating-rubocop-todo-files).
      
      If you have any questions, feel free to reach out in the `#f_rubocop` channel on Slack.
      
      ### Responsibility of Assignee
      
      We pick a random ~backend reviewer as the assignee. You should make sure to fix any merge conflicts if they
      arise and get this merge request merged like any other merge request authored by you.
      
      ### Responsibility of Reviewer
      
      Since these changes are simple we skip the initial ~backend review for efficiency and request a review from a
      random ~backend maintainer to review and merge these changes.
      
      This change was generated by
      [gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
      using the Keeps::GenerateRubocopTodos keep.
      
      To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
      label ~"GitLab Housekeeper" and consider pinging the author of this keep.
      
      Changelog: other
      845076c6
  7. Dec 23, 2024
  8. Dec 10, 2024
  9. Dec 05, 2024
  10. Nov 25, 2024
    • GitLab Housekeeping Bot's avatar
      Regenerate RuboCop TODO files · 2e875a0c
      GitLab Housekeeping Bot authored
      Due to code changes, some RuboCop offenses get automatically fixed over time. To avoid reintroducing these
      offenses, we periodically regenerate the `.rubocop_todo` files.
      
      While reviewing this merge request make sure:
      
        1. The files are only added, renamed or removed from the todo lists or the comments are updated and there
           should be no other changes.
        2. **rubocop**, **haml-lint**, and **haml-lint** jobs pass.
      
      Read more about this [automation here](https://docs.gitlab.com/ee/development/rubocop_development_guide.html#periodically-generating-rubocop-todo-files).
      
      If you have any questions, feel free to reach out in the `#f_rubocop` channel on Slack.
      
      ### Responsibility of Assignee
      
      We pick a random ~backend reviewer as the assignee. You should make sure to fix any merge conflicts if they
      arise and get this merge request merged like any other merge request authored by you.
      
      ### Responsibility of Reviewer
      
      Since these changes are simple we skip the initial ~backend review for efficiency and request a review from a
      random ~backend maintainer to review and merge these changes.
      
      This change was generated by
      [gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
      using the Keeps::GenerateRubocopTodos keep.
      
      To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
      label ~"GitLab Housekeeper" and consider pinging the author of this keep.
      
      Changelog: other
      2e875a0c
  11. Nov 04, 2024
    • GitLab Housekeeping Bot's avatar
      Regenerate RuboCop TODO files · 89dec256
      GitLab Housekeeping Bot authored
      Due to code changes, some RuboCop offenses get automatically fixed over time. To avoid reintroducing these
      offenses, we periodically regenerate the `.rubocop_todo` files.
      
      While reviewing this merge request make sure:
      
        1. The files are only added, renamed or removed from the todo lists or the comments are updated and there
           should be no other changes.
        2. **rubocop**, **haml-lint**, and **haml-lint** jobs pass.
      
      Read more about this [automation here](https://docs.gitlab.com/ee/development/rubocop_development_guide.html#periodically-generating-rubocop-todo-files).
      
      If you have any questions, feel free to reach out in the `#f_rubocop` channel on Slack.
      
      ### Responsibility of Assignee
      
      We pick a random ~backend reviewer as the assignee. You should make sure to fix any merge conflicts if they
      arise and get this merge request merged like any other merge request authored by you.
      
      ### Responsibility of Reviewer
      
      Since these changes are simple we skip the initial ~backend review for efficiency and request a review from a
      random ~backend maintainer to review and merge these changes.
      
      This change was generated by
      [gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
      using the Keeps::GenerateRubocopTodos keep.
      
      To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
      label ~"GitLab Housekeeper" and consider pinging the author of this keep.
      
      Changelog: other
      89dec256
  12. Oct 04, 2024
    • Abdul Wadood's avatar
      Regenerate RuboCop TODO files · 03732e45
      Abdul Wadood authored
      Due to code changes, some RuboCop offenses get automatically fixed over time. To avoid reintroducing these
      offenses, we periodically regenerate the `.rubocop_todo` files.
      
      While reviewing this merge request make sure:
      
        1. The files are only added, renamed or removed from the todo lists or the comments are updated and there
           should be no other changes.
        2. **rubocop**, **haml-lint**, and **haml-lint** jobs pass.
      
      Read more about this [automation here](https://docs.gitlab.com/ee/development/rubocop_development_guide.html#periodically-generating-rubocop-todo-files).
      
      If you have any questions, feel free to reach out in the `#f_rubocop` channel on Slack.
      
      ### Responsibility of Assignee
      
      We pick a random ~backend reviewer as the assignee. You should make sure to fix any merge conflicts if they
      arise and get this merge request merged like any other merge request authored by you.
      
      ### Responsibility of Reviewer
      
      Since these changes are simple we skip the initial ~backend review for efficiency and request a review from a
      random ~backend maintainer to review and merge these changes.
      
      This change was generated by
      [gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
      using the Keeps::GenerateRubocopTodos keep.
      
      To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
      label ~"GitLab Housekeeper" and consider pinging the author of this keep.
      
      Changelog: other
      03732e45
  13. Oct 02, 2024
  14. Sep 30, 2024
  15. Aug 21, 2024
  16. Aug 15, 2024
  17. Jul 24, 2024
  18. Jun 11, 2024
  19. May 16, 2024
  20. Apr 12, 2024
  21. Mar 25, 2024
  22. Feb 15, 2024
  23. Nov 22, 2023
  24. Nov 09, 2023
  25. Oct 27, 2023
    • Vasilii Iakliushin's avatar
      Remove Rugged patches · b1c64be7
      Vasilii Iakliushin authored
      Contributes to #421591
      
      **Problem**
      
      We are going to deprecate Rugged patches.
      
      **Solution**
      
      Remove Rugged patches related code:
      * Feature flags
      * Tests for Rugged
      * Rugged patches for Git objects
      
      Changelog: removed
      b1c64be7
  26. Oct 26, 2023
  27. Oct 25, 2023
  28. Oct 19, 2023
  29. Oct 05, 2023
  30. Sep 12, 2023
  31. Sep 07, 2023
  32. Sep 06, 2023
  33. Aug 08, 2023
  34. Jul 07, 2023
  35. Jul 06, 2023
  36. May 10, 2023
  37. Apr 27, 2023
  38. Apr 20, 2023
Loading