![]() ![]() Probably the most interesting feature of the extension is the ability to checkout the branch of the Pull Request directly from the editor. The UI interaction is the same as on GitHub, you can add a comment by clicking on the line number and then clicking on the “Add comment” button or by dragging the mouse over the lines you want to comment, in case of a multiline comment. Speaking of comments, we just saw you can add some to the Pull Request, but you can also add comments to specific lines of code and files! You can for example edit labels, assignees, reviewers, and even add comments. It’s not readonly though, but you can fully interact with it from the editor. If you click on “Description” from the sidebar, you’ll see the Pull Request overview:įrom here you can see all the relevant information you can also find on the web UI on GitHub. When clicking on one of them a Diff Editor will open so that you can see the changes made to the file by comparing them to the base branch. The first thing you notice when selecting a Pull Request from the sidebar is the changed files. Opening it the first time will ask you to login to GitHub, just click on the button and a browser tab will open where you can login to your GitHub account. The new one is called “GitHub Pull Requests and Issues”.Īs soon as the extension is installed, you’ll see a new icon in the Activity Bar on the left side of Visual Studio Code: Note: make sure to not get confused, the extension called “GitHub” is an old one and deprecated. You can find it in the marketplace by searching for “GitHub” or by clicking here. ![]() The first thing you need to do is to install the official GitHub Pull Requests and Issues extension for Visual Studio Code. (If you already installed the extension last week, you can skip this step!) (I mean, if you want to watch the video and leave a like, that would be awesome! □) Install the official GitHub Extension Not a fan of video content? No problem, as usual I write down the concepts explained in the video in written form as well! ![]()
0 Comments
Leave a Reply. |