After master is up to date, we are switching back to TESTĤ. In my case as you can see it did not work because I had one commit which was not posted to main, in this case you can do resync/update from the VS extension, to get the latest version:ģ.
use git checkout master to ensure that branch is up to dateĢ.
Now we are going to merge main into our pull request branch for testing, mainly we need to make sure here that master is up to date and start merging:ġ. With GitLens, it’s so easy to view code authorship, check commit number, view changes between the last commit and existing changes, and so on. Let’s get this pull request as a branch locally with GitLens is the visual studio code plugin to supercharge git capabilities. The latest version of Microsoft’s Visual Studio Code code editor focuses on improvements to the toolbar and autoscrolling, as well as Git repos. Pull request is being created based on the branch in this case I took movingtoRC one as I want ask someone to check my changes and confirm that I can merge them to the main one:Īs we have now our pull request ready, we can see that it received an identifier #6 Normally we always need to test the whole set of code before accepting a git pull request, in this article we will try to understand the best approach to deal with pull requests and test them locally.įirst, we need to get and setup visual studio github extension we won’t go through the way of setting up it, because this process is very well documented and just start from creating a pull request in the visual studio:
0 kommentar(er)
