-
Notifications
You must be signed in to change notification settings - Fork 3
Backport test PR #11
Backport test PR #11
Conversation
|
@gitbot backport backport-target |
|
Backport Job to branch backport-target Created! The magic is happening here |
|
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7880058 for more details. |
|
@gitbot backport backport-target |
|
Backport Job to branch backport-target Created! The magic is happening here |
|
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9897468 for more details. |
|
@gitbot backport backport-target |
4 similar comments
|
@gitbot backport backport-target |
|
@gitbot backport backport-target |
|
@gitbot backport backport-target |
|
@gitbot backport backport-target |
|
Backport Job to branch backport-target Created! The magic is happening here |
|
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9898086 for more details. |
|
@gitbot backport backport-target |
|
Backport Job to branch backport-target Created! The magic is happening here |
|
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9898226 for more details. |
To test backporting:
v1.0-testtag with the changes you want to test (i.e., update the tag based on your topic branch)Check the
Actionsmenu above for the status of the backport GitHub action that is triggered; particularly, if the backport bot does not add status comments to this PRIf successful a new backport PR against the
backport-targetbranch will be created. Recommend simply closing that PR without merging it to preserve the pending change for a subsequent backport testWhen you've completed your testing, please delete all of the comments you've added to this PR to help reduce clutter