Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 38,034
    • Issues 38,034
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,346
    • Merge requests 1,346
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #231032

Closed
Open
Created Jul 22, 2020 by Robert Speicher@rspeicherOwner

Allow for cherry-pick and revert "dry runs"

As part of gitlab-com/gl-infra/delivery#1009 (closed), teamDelivery needs to be able to know if a cherry-pick will apply cleanly to a target branch, but without actually applying the change. This will allow us to inform developers that a security fix requires a manual backport to a previous stable branch, or if we can simply cherry-pick their merge request targeting the main branch.

While we have no need (yet) for a revert dry-run, we can add that functionality at the same time since the APIs are nearly identical both in gitlab-rails and in Gitaly.

Assignee
Assign to
13.3
Milestone
13.3 (Past due)
Assign milestone
Time tracking