Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

create_service.rb

  • Timothy Andrew's avatar
    e805a647
    Backport changes from gitlab-org/gitlab-ee!581 to CE. · e805a647
    Timothy Andrew authored
    !581 has a lot of changes that would cause merge conflicts if not
    properly backported to CE. This commit/MR serves as a better
    foundation for gitlab-org/gitlab-ee!581.
    
    = Changes =
    
    1. Move from `has_one {merge,push}_access_level` to `has_many`, with the
       `length` of the association limited to `1`. This is _effectively_ a
       `has_one` association, but should cause less conflicts with EE, which
       is set to `has_many`. This has a number of related changes in the
       views, specs, and factories.
    
    2. Make `gon` variable loading more consistent (with EE!581) in the
       `ProtectedBranchesController`. Also use `::` to prefix the
       `ProtectedBranches` services, because this is required in EE.
    
    3. Extract a `ProtectedBranchAccess` concern from the two access level
       models. This concern only has a single `humanize` method here, but
       will have more methods in EE.
    
    4. Add `form_errors` to the protected branches creation form. This is
       not strictly required for EE compatibility, but was an oversight
       nonetheless.
    e805a647
    History
    Backport changes from gitlab-org/gitlab-ee!581 to CE.
    Timothy Andrew authored
    !581 has a lot of changes that would cause merge conflicts if not
    properly backported to CE. This commit/MR serves as a better
    foundation for gitlab-org/gitlab-ee!581.
    
    = Changes =
    
    1. Move from `has_one {merge,push}_access_level` to `has_many`, with the
       `length` of the association limited to `1`. This is _effectively_ a
       `has_one` association, but should cause less conflicts with EE, which
       is set to `has_many`. This has a number of related changes in the
       views, specs, and factories.
    
    2. Make `gon` variable loading more consistent (with EE!581) in the
       `ProtectedBranchesController`. Also use `::` to prefix the
       `ProtectedBranches` services, because this is required in EE.
    
    3. Extract a `ProtectedBranchAccess` concern from the two access level
       models. This concern only has a single `humanize` method here, but
       will have more methods in EE.
    
    4. Add `form_errors` to the protected branches creation form. This is
       not strictly required for EE compatibility, but was an oversight
       nonetheless.