{"id":11757,"date":"2019-06-06T12:56:04","date_gmt":"2019-06-06T20:56:04","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/vsnews\/?p=11757"},"modified":"2019-06-06T12:56:04","modified_gmt":"2019-06-06T20:56:04","slug":"aa5anzj","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/vsnews\/akams-aa5anzj\/","title":{"rendered":"Improving Azure DevOps cherry-picking"},"content":{"rendered":"<p>One of the more powerful git commands is the <a href=\"https:\/\/git-scm.com\/docs\/git-cherry-pick\">cherry-pick<\/a> command. This command takes one or more existing commits and applies each commit\u2019s changes as a new commit on a different branch. This can be an extremely powerful component of many git workflows such as the Azure DevOps team\u2019s <a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/devops\/learn\/devops-at-microsoft\/release-flow#releasing-hotfixes\">Release Flow<\/a>. To highlight a common use-case for it, let\u2019s talk about hot-fixing release branches.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the more powerful git commands is the cherry-pick command. This command takes one or more existing commits and applies each commit\u2019s changes as a new commit on a different branch. This can be an extremely powerful component of many git workflows such as the Azure DevOps team\u2019s Release Flow. To highlight a common [&hellip;]<\/p>\n","protected":false},"author":836,"featured_media":8227,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3,8],"tags":[],"class_list":["post-11757","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allskus","category-vs4mac"],"acf":[],"blog_post_summary":"<p>One of the more powerful git commands is the cherry-pick command. This command takes one or more existing commits and applies each commit\u2019s changes as a new commit on a different branch. This can be an extremely powerful component of many git workflows such as the Azure DevOps team\u2019s Release Flow. To highlight a common [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts\/11757","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/users\/836"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/comments?post=11757"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/posts\/11757\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/media\/8227"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/media?parent=11757"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/categories?post=11757"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vsnews\/wp-json\/wp\/v2\/tags?post=11757"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}