VS Code Source Control Pane is Blank - visual-studio-code

I've reinstalled my PC and tried connecting back up to my Azure DevOps Repo using VS Code and TFVC. I'm using TFVC Location with Visual Studio 2019 Community TF.exe. It all seems to work and I can connect to my repo with my credentials. It all seems to load up fine and I can even see TFVC with a number of changes/differences. - see image below. However I'm expecting to see my source control and list of files to commit like before. But the panel is blank. There's no errors in the Output window of VS Code either.
I've tried removing and re-adding the workspace. Tried editing/adding anew file to the project in hope of kickstarting TFVC pane to show the file list. - the number next to TFVC updates but I don't see any menu button or files list.
Has anyone else had this and know a solution, or know where I'm going wrong.

Just toggle "scm.alwaysShowProviders" on and off from whatever value your have (default is false), this would cause the source control pane to redraw and fix the issue for now.

I believe per the issues in GitHub that this issue is fixed for most people as of VSCode version 1.39.2, but I was still seeing it for projects based on a Git repo.
After some trial and error I found this setting was the culprit: "scm.alwaysShowProviders": true
When I remove that setting, or set it to false, my Source Control pane works correctly.

This happens to me occasionally. I just figured out I can fix this by right clicking in the blank area and then selecting the repository I want to show up

Issue opened on GitHub: https://github.com/microsoft/vscode/issues/82374
For now I've rolled back to the August update and that's resolved it.

Clicking the blank area and slecting repo does the trick

I had this problem on the 1.55 version, as it's centrally controlled I couldn't manually update, but when they pushed the 1.64 version through, the problem has gone away, was driving me mad!

Related

How to show one's own forked-repo Issues in VS Code?

I forked tidythemes/blankslate to robertandrews/blankstrap.
I created new Issues for myself, for my own fork...
But, in VS Code, in the GitHub extension panel, I am instead seeing the Issues for the original blankslate...
I would like to be seeing my own Issues in VS Code.
Source Control Repositories shows...
Branch switcher shows...
Switching to another (ie. origin/master Remote) does not result in my Issues showing.
What must I do to get my own Issues visible?
Developer of the VS Code GitHub Issues extension suggests it may be a bug.

View changes gitlab in visual studio code

I am using visual studio code to develop my flutter app.
I need to share it with a colleague. I was able to make the transfer on gitlab very easily.
I have a problem.
When my colleague makes changes to my code, before "taking" his changes I would like to be able to view them on visual studio code.
I have tried several avenues, but each time my code is synchronized and modified according to the changes made
Can anyone help me?
1:Click Git icon on left side of VS Code
2:If you've made changes to the file(s) since last commit, you'll see the file(s) listed under "CHANGES"
3:Right click the file name (under "CHANGES") and click "Open Changes"
4:This will open the two versions of the file side by side with the changes highlighted
I believe this is how you see the changes that your college made on GitLab

Subtree Dissappears from Sourcetree

I am creating successfully a subtree to a remote repo and pull/push successfully using Sourcetree. The substree repo appears below "Stashes" tab on the left of Sourcetree as "Subtree" tab.
However, when I close and reopen the Sourcetree, the "Subtree" tab and the subtree that I have defined earlier, disappears.
It does not disappear, if I close the project tab and reopen the project without closing the Sourcetree.
I have seen these two post with the same/similar problem:
First Post
Second Post
Both links belong to the same person.
I have tried the suggested solution there (clearing cache) but it did not solve my problem.
The person, who was in charge of developing this part of the Sourcetree, has not posted since 2017. Maybe he left Atlassian, and this issue is still there.
I have already asked this question in the Sourcetree forum, but no replies since April.
I have opened a bug report at this link
I have tried version 3.3.9 and the problem is still there.
It seems to be a simple "save" issue. I also remember that Sourcetree did not have this issue in the earlier versions.
I found out that this is consequence of another major issue with Sourcetree versions came after 3.2.6. After this version, a major bug is introduced, probably something related to authentication, and it results a constant red exclamation mark on the remote button. This mark can be fixed in version 3.2.6, but not in the later versions. So, I am staying with version 3.2.6 for now.

VSCode Extension does not show contributions

When you install my extension, and you click on "Contributions" in VSCode, it only shows a blank page.
enter image description here
I have no clue why that is.. the package.json looks fine though..
How can I show the contributions like any other extension does?
This was a bug in VS Code 1.27. It is fixed in VS Code 1.28+
I used to have the same issue!
I used to create new branches for different lessons learned which were never part of the main branch.
Merging the branches to main(master) updated my contributions.

Eclipse Git "Commit Changes" missing file [duplicate]

I have been using EGit to upload my stuff to github for a few months now.
But off late I do not see what files have been changed, and I dont know why. Please help.
As you can see I have updated some files and I cannot see a list of files in the files section.
This looks like a problem with Mac OS X 10.10 and SWT, see Eclipse bug 446534 for details.
Note that the heading above the table says "Files (1/1)", so EGit calculated the changed files correctly, but it isn't visible. Try if resizing the window makes it appear.
The Git Staging view, which is another way to commit using EGit doesn't seem to have the same problem. Maybe you could consider using that instead of the Commit dialog, see the user guide.
As the comment 2 at the Eclipse bug 446534 mentioned, calling table.pack() will solve this problem for a single tableviewer.