Clarify PR migration request - awaiting specific forked PR details #21349
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
This PR was created in response to a request: "Can you take the changes from this PR and open a new PR from this repo instead of forked repo". However, the request lacks specific details needed to proceed with the implementation.
Issue
The problem statement is ambiguous for the following reasons:
microsoft/azure-pipelines-tasks, not from a forked repositoryWhat's Needed
To proceed with this task, please provide one of the following:
Repository Context
The repository already contains automation scripts for PR creation:
ci/open-pullrequest.ps1- Creates PRs using GitHub CLIci/courtesy-push/open-courtesy-push-pull-request.js- Creates courtesy bump PRsci/courtesy-push/open-hotfix-pr.js- Creates hotfix PRsThese existing scripts work with branches in the main repository. If the goal is to extend this functionality to support forked PR migration, specific requirements would be helpful.
Next Steps
Once the specific forked PR or detailed requirements are provided, I can:
Status: Awaiting clarification before proceeding with implementation.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.