In a previous article, we talked about the new news of which GitHub allows you to create an unlimited number of private repositories with their free GitHub Free offer.
This announcement, among many others that have been made in recent months, appears to be the result of Microsoft's acquisition of GitHub.
An operation that aims not only to accelerate the adoption of the source code exchange platform in business, but also to bring Microsoft products to new markets.
The two companies also promised to integrate their products to provide developers and businesses with new source code sharing and collaboration experiences.
Y This began to take shape, during the month of last September when Microsoft announced Azure Pipelines(a new Integration and Continuous Deployment (CI / CD) service built on GitHub) and a public preview of the GitHub Pull Requests (PR) extension for Visual Studio Code.
We must emphasize that pull requests are used by collaborative or open source projects to propose patches or new features.
Microsoft wants to connect its products
With this extensionMicrosoft offers a new pull request management experience to Visual Studio Code users.
Allowing them to collaborate, comment on, review, and validate GitHub PR right from the code editor.
As one of the main features, allows you to authenticate and connect the code editor to GitHub and thus be able to list and navigate PRs from Visual Studio Code.
Among other possibilities, terminal integration is still offered so that the Visual Studio code interface and command line tools like git can coexist.
This VS Code extension comes, as Microsoft has explained, filling a void in workflow that millions of engineers encounter every day.
To put this gap in perspective, Microsoft reiterated the pull request experience today:
“Today, when reviewing source code, many of us are forced to let our editors use a simplified web interface or a third-party review tool that displays changes in a different editor.
This allows you to get an overview of the changes, but most of the time you don't have full context on how the changes were made and how they affect the surrounding source code.
Outside of your normal coding environment, you don't have the keyboard shortcuts, your favorite themes, and customizations.
Worse, this means that you don't have an environment to navigate through the source code and verify that the changes you are reviewing are working correctly. «
About VS Code Pull Requests
Since the release of the first public preview of GitHub PR for Visual Studio Code, Microsoft has made many improvements to their tool.
And like GitHub on its official blog, With the latest version of the extension it is now possible to create GitHub pull requests directly in Visual Studio Code and not just manage from the code editor.
To create pull requests in VS Code, simply the user must hover over the heading "GitHub Pull Requests" and click the + sign.
Then choose the target branch of the pull request and hit "enter" to open your RP.
VS Code Pull Requests provides many other small improvements that you can see in the release notes available in the project repository.
You can also, on GitHub, download the latest version of the extension. Note that VS code pull requests can also be installed or updated directly from VS Code.
In addition to the ability to create pull requests now, with the latest version of the Visual Studio Code, you can suggest changes to the comments and view the health checks for each RP.
For suggestions on code changes, you can leave them as comments with a diff indicating the current code next to the suggested changes.
Hints can be easily applied by selecting Apply Patch to validate the new code patch.
If you want to know a little more about it you can visit the following GitHub article