![]() ![]() Show file history from quick launch view in Fork As you can see in the screenshot below, with this feature you can access the history with only one click and one “paste-action”. Show file history from quick launch view in ForkĪnother way to quickly display the version control history for a specific file is the feature “show file history” from “quick launch view” of Fork. When you´re done with your inquiry you can simply undo your changes within the changes window. So if you what to see the history for a specific element I would recommend to save a small change to the file, so you can access it via the changes window. If you open the pending changes you can compare the changes with the unmodified version und you are also able to jump the history of the file. In the footer bar you can see the pending changes for your currently selected repository. The more comfort way is to use the footer bar in Visual Studio. You can see the setup on the picture below. As a side note you can specify the branches which get considered for code search. If you want a more specific search result you can change the search option from “Relevance” to “File Name”.Īs you can see in the picture above you can jump from the web interface directly to history, compare and blame. SalesTable to the generic search field of Azure DevOps. ![]() ![]() The only thing you have to do is copy/past the element name e. I know that it is a bit more work to navigate to source control history using Azure DevOps, but it is quite straight forward. In this post I want to highlight some alternatives for showing source control history. With this process the project file or visual studio tries to find the link to version control for the file in your AOS folder and not in your repository folder which is linked to your AOS folder. The reason behind is the symbolic link, we are using to map multiple repositories into the same AOS folder. If you using Git with Microsoft Dynamics 365 for Finance and Operation as described in one of my previous posts you will notice that you don´t have the ability to view the version control history of individual elements directly from the solution explorer in Visual Studio.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |