Skip to main content

Azure DevOps Fork Repos between two Organization

 

Azure DevOps Fork Repos between two Organization


This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple.

The idea is to fork my Azure DevOps Repo to a different organization and push changes between them.


Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization.

I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement.


  1. Import Repo to the new Organization

    1. Remember here you have to generate a personal token to be able to import the Repo

    2. you have to be a member of the new organization as well

  2. This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes

  3. So far all looks good, you can clone the solution in your new Organization, branch and do all the amazing things that git provides.

    1. Few things to remember here:

      1. Your changes are merged in the master of your new organization

      2. Question is what can you do to push your changes from the new Organization to the to the Previous Organization where you have imported your repo?

The simplest way to do the synchronization is to configure your Git Repository Setting Remotes, I have included a screenshot 



This will give you the capability to push and fetch changes from the Organization that the code has been generated.

Labels:

Comments

  1. AnonymousApril 13, 2023 at 8:46 AM

    I really like your suggestion. I just have one issue. Which is that I have to push twice for both organization separately from Visual Studio. If you have a solution which pushes in both organization in one go then I would really appreciate your help.

    ReplyDelete
  2. AnonymousApril 14, 2023 at 12:48 AM

    This works for me but I have to push and fetch twice for both organization.

    ReplyDelete
  3. AnonymousOctober 18, 2023 at 4:43 AM

    It's excellent. Saved my time.

    ReplyDelete

Post a Comment

Popular posts from this blog

Power Platform Tool for Visual Studio 2019/2022

 Power Platform Tool for Visual Studio 2019/2022 We have a new Visual Studio Extension Power Platform Tool.  Creation and deployment of Plugins, Custom Workflows and WebResources is going to be easy and time saving.  This article is going to focus on how to connect to your environment and create your Visual Studio Solution. In a subsequent article I will try to cover on how to Create and deploy your components to your environment. Installation is straight forward go to      Tools→ Manage Extensions→ Search for Power Platform Tools     You will Need Visual Studio 2019 or later version     Subsciption to Pawer App/Dataverse or trial       .Net Framework 4.6.2 Now we will go over how to create a Project and connect it to your Environment Open Visual Studio 2019 →New Project Search for Power Platform Solution Template Add Project Name and Location → Create Click on Start from Dataverse to connect to your environment Enter the following and → Login
7 comments
Read more

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.
Post a Comment
Read more