Azure CI - Pull Request issue RRS feed

  • Question

  • Hi Guys!

    1. I have got a public git repository on the following path:
    2. I committed and pushed there some data (simple hello world console app) from my local PC.
    3. I created a new public project in MS Azure.
    4. I set up a new Repos so that it imported my git sources: (https://askoldthefirst.xp-dev.com/git/Biz)
    5. Then, on my local PC, I created a new git branch. Switched to it.
    6. And committed and pushed some new changes to my recently created branch.

    Up to now, everything looks fine for me.

    But: When I tried to create a new Pull Request (in MS Azure) to merge changes from my branch to the master one
    I could not see my branch in a list of branches.

    I just could see only the initial master branch in the list of branches.

    So currently I can not do any pull requests and I guess I do something wrong or I did not do something in MS Azure environment to solve this issue.

    Can you please help me with this problem? I would really appreciate you!

    Thank you!



    Regards, Askold The Second

    Tuesday, September 3, 2019 5:01 PM


All replies

  • Hi AskoldTheSecond!

    The Azure DevOps team and community are active and answering questions on https://developercommunity.visualstudio.com/spaces/21/index.html can you please post your question there instead? This forum is specifically for Azure App Configuration questions.


    Tuesday, September 3, 2019 5:59 PM
  • Thank you!

    I posted it there.

    Regards, Askold The Second

    Tuesday, September 3, 2019 7:28 PM
  • Also try asking for help over here.




    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, September 4, 2019 1:32 AM
  • Hello AskoldTheSecond,

    First off, please be aware that importing your Git repo into an Azure repo is like a one-time task and does not automatically keep either in sync with the other. Please check the discussion here to get more insight.

    Moreover, it is always best to maintain only either of the repos (GitHub/Azure Repo) after the import in order to avoid any sort of confusion, so there's only one source of truth. Hence, consider cloning your Azure Repo to continue with further Development, as shown in the screenshot below:

    Please refer to the following quickstarts to get going:

    Hope this helps!

    Friday, September 13, 2019 7:17 PM
  • Hello AskoldTheSecond,

    Hoping the above response helped. Please let us know otherwise and we can explore further.


    Tuesday, September 24, 2019 9:04 AM