How to view inline diff of multiple files at once in VS Code? - visual-studio-code

In VS Code, for a given commit I would like to see inline diffs from all files in one view or page, so that I would not have to click to see diffs for each file separately.
I can't find any extension that would do this.
Basically I'm looking for a feature like there is in Bitbucket when you click on a given commit, and you see all the differences in one page. Something like in the picture below.

in the SCM bar you have a COMMITS view
context click a commit and Select for Compare
context click another commit and Compare with Selected
Now in SEARCH & COMPARE view you can click a changed file and see a diff

Related

VSCode Source Control Icon view has too many entries; how do I reduce them?

I'm a newbie at VSCode and Git. After seeing videos, I understand using Git from the command line.
I did a Git init on an existing project folder. 5 items in the directory were shown as untracked when I execute a git status in the terminal.
When I click on the Source Control Icon in the sidebar there are over 300 items shown as untracked??
When I do a git add in the terminal for each of the 5 items previously shown as untracked, the view from the Source Control icon now shows over 300 items marked as "A".
Why must I be shown all these 300+ items when in the terminal I am only working with 5? I'd like to see only the 5 items in the terminal listed in The Source Control view. Having over 300 items is overwhelming.
Is there a way to stop so many items from being displayed in the Source Control view? Do I even want to do that?
You can show git changes as a tree (from Settings):
"scm.defaultViewMode": "tree"
There's also an icon to toggle it:
If that's not what you are asking for, then add the files that you want to ignore to the .gitignore file to exclude them from the SCM view.

VS Code - Search in Source Control View

Is there a search feature that we can use to search the files in the Source Control View (in the Activity Bar)? Let's say we have tens of files changed and when we go to the Source Control view, how do I find and add a specific file to the Staged state by using the UI?
Just pick any of files and start to type filename you want to find. Then typed text appear in the right upper corner of SCM View and you can filter out searched files.
See how it looks:
Also this way works in the Explorer view.
Upd. Official description of feature: https://code.visualstudio.com/docs/getstarted/userinterface#_filtering-the-document-tree

Github UI - cannot edit file further after viewing in preview pane

I want to create a README.md file using the Github edit/preview file interface.
The problem is when I switch to the Preview pane and then back to the Edit pane, I can see a cursor blinking at the very top of the document but cannot move it or perform any further editing.
If I want to add/modify content I need to cancel the entire operation and start again from scratch. Needless to say, this isn't optimal. Is there something I am missing here? Or is it simply not possible? Any pointers much appreciated.
One option is to save the README as is.
Since July 2018, you now have a button to edit it further.
Button to edit a repository's README from the repository root
If you have permission to push to a repository, you can now edit a README file from the repository root by clicking the pen icon to the right of the README’s file header.
Learn more about editing files in your repositories here.

Compare changes with latest from repo

Eclipse shows me with the symbol > which files I have modified, after the last repository update. Before commiting, I want to see the changes I made.
When I go right click->Team->Synchronize with repository I get exactly what I want. The problem is, I only get the view for this one file I clicked. I need to change the view back to Java, to be able to chose the next modified file.
Is it possible, to compare all modified files, one by one, with the latest edition from the repository, without changing the view after each file?
Instead of right clicking a specific file, you can right click the entire project and perform the same operation you describe.

Xcode SCM - Need help with checking files back in!

Okay, I have another newbie question. I'm starting to work with a remote code repository, remotehosting.com, and have been given a username, password, and URL. I've been able to successfully associate my project with a remote source code repository, have checked out/pulled down the source files, and have now made a small change to a single file. Here's where my questions start.
1) I can't see anywhere in my GUI where Xcode realizes that I have made a change to a file
2) How do I check my files back in?
I gotta be missing something. The docs I've been reading point to more menu items that I currently see under my SCM menu item. Anybody have any ideas? Thanks in advance for your assistance!!!
File -> Source Control -> Commit, Select the files that you want to commit, add a comment and hit commit button.
This is the flow for xcode 4
In Xcode 3...
The Project window should have a column which displays the SCM status for your files. This can appear both in the "Groups & Files" outline view in the left pane and the file list in the right pane. The icon for the column is a little cylinder shape, a black-and-white version of the yellow cylinder that's shown when you manage repositories. If this column is not displayed, you can right-click on the header of either of those panes to bring up a menu with a list of columns. Select "SCM" from that. The status will display as the same one-letter codes that SVN uses on the command line.
In order to commit files, you can either a) select the particular files, or group you want to commit and use the menu command SCM>Commit Changes..., or b) Select SCM>Commit Entire Project... (which I personally have bound to ⌥-⌘-C in the Xcode key bindings preferences).
Either of these will display a sheet in which you can enter your commit message; the text field in this is very handy in that it accepts the Return key as a newline, rather than passing it to the "Commit" button, but could be confusing the first few times. Press ⌘-Return to activate the button and perform the commit.