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

push.rb

  • Luke Duncalfe's avatar
    1883e320
    Use Gitlab::PushOptions for `ci.skip` push option · 1883e320
    Luke Duncalfe authored
    Previously the raw push option Array was sent to Pipeline::Chain::Skip.
    
    This commit updates this class (and the chain of classes that pass the
    push option parameters from the API internal `post_receive` endpoint to
    that class) to treat push options as a Hash of options parsed by
    GitLab::PushOptions.
    
    The GitLab::PushOptions class takes options like this:
    
        -o ci.skip -o merge_request.create -o merge_request.target=branch
    
    and turns them into a Hash like this:
    
        {
          ci: {
            skip: true
          },
          merge_request: {
            create: true,
            target: 'branch'
          }
        }
    
    This now how Pipeline::Chain::Skip is determining if the `ci.skip` push
    option was used.
    1883e320
    History
    Use Gitlab::PushOptions for `ci.skip` push option
    Luke Duncalfe authored
    Previously the raw push option Array was sent to Pipeline::Chain::Skip.
    
    This commit updates this class (and the chain of classes that pass the
    push option parameters from the API internal `post_receive` endpoint to
    that class) to treat push options as a Hash of options parsed by
    GitLab::PushOptions.
    
    The GitLab::PushOptions class takes options like this:
    
        -o ci.skip -o merge_request.create -o merge_request.target=branch
    
    and turns them into a Hash like this:
    
        {
          ci: {
            skip: true
          },
          merge_request: {
            create: true,
            target: 'branch'
          }
        }
    
    This now how Pipeline::Chain::Skip is determining if the `ci.skip` push
    option was used.