Skip to content

Conversation

@dibarbet
Copy link
Member

@dibarbet dibarbet commented Apr 16, 2025

@ghost ghost added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 16, 2025
@dibarbet dibarbet force-pushed the dev/dibarbet/cherry_pick_pipeline branch from 0844d9e to aaa80ec Compare April 16, 2025 23:21
type: boolean
default: true

- name: VisualStudioCherryPickSHA
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not clear what this does ... can you add a comment describing what this parameter is used for?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh ... so this lets us pick a commit of VS that we want to run against? Basically means we can retest a change against the same VS baseline?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not exactly - it allows us to cherry-pick a commit from another VS branch onto our insertion branch. For example if we need to do a dual insertion, or a roslyn change requires another VS-side change. Instead of having to wait for the PR to be created, then cherry-pick it over, the roslyn insertion tool can do it when it creates the insertion

@dibarbet dibarbet marked this pull request as ready for review April 17, 2025 23:16
@dibarbet dibarbet requested a review from a team as a code owner April 17, 2025 23:16
@dibarbet dibarbet merged commit b0da3f2 into main Apr 22, 2025
28 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Apr 22, 2025
@RikkiGibson RikkiGibson modified the milestones: Next, 18.0 P1 Aug 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants