Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Sep 30, 2025

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:

  1. No specific forked PR referenced - The request mentions "this PR" but doesn't identify which forked repository PR contains the changes to be migrated
  2. Current PR is already from main repo - This PR (Clarify PR migration request - awaiting specific forked PR details #21349) originates from microsoft/azure-pipelines-tasks, not from a forked repository
  3. Unclear scope - It's not clear whether this is requesting:
    • Migration of a specific PR's changes from a fork to the main repository
    • A tool or script to facilitate PR migration workflows
    • Documentation on the PR migration process

What's Needed

To proceed with this task, please provide one of the following:

  1. Specific PR to migrate: The PR number or URL from a forked repository whose changes should be copied
  2. Fork and branch details: Owner and branch name containing the changes to migrate
  3. Alternative interpretation: If this is requesting a general tool/documentation, please clarify the requirements

Repository Context

The repository already contains automation scripts for PR creation:

  • ci/open-pullrequest.ps1 - Creates PRs using GitHub CLI
  • ci/courtesy-push/open-courtesy-push-pull-request.js - Creates courtesy bump PRs
  • ci/courtesy-push/open-hotfix-pr.js - Creates hotfix PRs

These 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:

  • Apply the changes from the forked PR to this branch
  • Create a utility script to automate forked PR migration
  • Document the manual process for maintainers

Status: Awaiting clarification before proceeding with implementation.

Original prompt

Can you take the changes from this PR and open a new PR from this repo instead of forked repo


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Can you take the changes from this PR and open a new PR from this repo instead of forked repo Clarify PR migration request - awaiting specific forked PR details Sep 30, 2025
Copilot finished work on behalf of tarunramsinghani September 30, 2025 10:11
@tarunramsinghani
Copy link
Collaborator

can you take changes from #21340 and port it over to this PR

@tarunramsinghani tarunramsinghani deleted the copilot/fix-04926fe2-fea3-4e5a-be36-4ab3f07751d9 branch September 30, 2025 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants