Hey I just updated Sourcetree on my mac to the latest version (2.2).
Where did git-flow go?
And how do I re-enable this functionality?
I just lost myself without it!
I have the same problem here, you can still use Git-Flow
From the menu: "Repository-> Git flow /HG flow -> Next action"
Using the hotkey: "⌥+⌘+F.
But still not able to get the button back... :/
On the download page the button is also gone:
https://www.sourcetreeapp.com/
Alternative you can download the previous version here:
http://downloads.atlassian.com/software/sourcetree/SourceTree_2.1.dmg
https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.7.0.32509.exe
UPDATE:
The have a new version of SourceTree Mac v2.2.2(51) / Win: v1.8.2 and when you have this version you can customize you toolbar by clicking on the toolbar with your right mouse button. Then you can enable the git flow button.
Downloads:
Mac v2.2.2:
https://downloads.atlassian.com/software/sourcetree/SourceTree_2.2.2.dmg
Windows v1.8.2:
https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.8.2.exe
Here is what you can do if you have SourceTree v2.2.3. (I'm sorry but I don't have enough reputation points to attach the image)
Edit: Now I can upload the GIF, thanks!
Enabling Git-Flow button SourceTree - GIF
The corresponding Windows version is 1.8.1.0.
The hotkey is Alt+Shift+F
UPDATE: It appears that Atlassian has pulled release 1.8.1.0. When you download now, you get version 1.7.0.
Jens Schumacher has just wrote that the git-flow button will be back in the next bugfix release. As for now, as others suggested, either roll back to a previous version, or use a hotkey (Alt+Shift+F for Windows, ⌘+⌥+F for OS X).
Git-Flow button is back as of update 1.8.2.0. So this issue should be resolved: just update SourceTree and it will be back.
As many people say here, you can use the hotkey
for OSX ⌘+⌥+F
for Windows Alt+Shift+F
But, also you can configure the toolbar to show the gitflow icon again. You just have to do a right click on the toolbar, select "customize toolbar..." and drag the icon back to the place it use to be. As simple as that.
I hope it helps.
Related
Some days ago vscode started showing the following interface any time I had a git conflict:
But I don't like it and want the regular one, the one that looks like this:
How can I modify the configurations to change this interface, I've explored hundreds of settings in vscode but haven't found the right one.
Thanks a lot in advance.
There is a setting called "git.mergeEditor" disable it then you have the old view back !
#Cristian Diaz Please refer to the latest version (1.71.0) Release note. They didn't remove the old merge conflicts resolution. We can enable it by clicking on the file icon.
With one of the latest updates to the VSСode, the expandable blocks with the list of branches, stesh, local history, etc. disappeared in the version control panel.
And if you right-click on the modified files, there is no stash changes option.
Questions:
How to see blocks with a list of branches, stashes, etc. again.
How to return to the context menu of the modified files the item for working with git stash?
UPD 21.08.22: the problem was in GitLens, which I removed. Reinstalling GitLance brought back all the items I needed.
Go to vs code extensions, install the gitLens extension pack.
gitLens
Latest version of vscode does not hide this. If you want to bring it back, you just need to Right Click on SOURCE CONTROL bar then pick the feature you want to display.
the problem was in GitLens, which I removed. Reinstalling GitLance brought back all the items I needed.
I installed GitLens in VS Code. Then it asked if I wanted to try the GitLens+ features. I clicked "Yes". Now I am stuck at the welcome screen and can't get past it. Any ideas how to get rid of this annoying screen?
Uninstall gitlens extension. Productivity extensions shouldn't reduce productivity by putting up adds that can't easily be closed.
I had the same problem, but I was able to solve it by following the steps below.
Open the sidebar extension
Click the down arrow to the right of the uninstall
Install another version
Install 11.7.0
Reload
But there was no Gitlens in the sidebar
So next
"git lens: show welcome view" in the command palette
Select "git lenses layout" in "view" of "quick setup"
Gitlens is displayed in the sidebar
Then install the latest version
Gitlens is displayed in the sidebar
I hope it helps you even a little.
Go to VS Code command Pallete and select GitLens+: Sign out of Gitlens+
that should get you to the previous experience.
you can also use the the VSCode Command Pallete to display the views you want, such as
I think I had the same issue on Windows (now I'm on my mac) so I went back to Windows, created a new account, and started the trial since logging off of my account on Windows didn't result in that scenario.
I couldn't reproduce it on Windows either.
I'm thinking that might be a glitch, I'm sure you already tried to close VSCode and open again, so, maybe try to sign out and sign in again.
If you want to remove the "home" view, use the elipses on the top right and untick it. Also, check if the other views are enabled.
The problem here is that when we install GitLens extension then all the GitLens features and buttons are added under the generic source control tab (Ctrl+shift+G). Even though GitLens creates a new tab of its own and it looks like all features and buttons are hiding behind the welcome screen. This is not the case and everything but the welcome screen is under the generic source control tab. Poor design choice indeed.
Hide GitLens+ Features from the Command Palette GitLens+: Hide GitLens+ Features
To restore from the Command Palette GitLens+: Restore GitLens+ Features
Step 1. Uninstall GitLens
This avoids fiddling with settings to try to stop it being nag-ware.
Step 2. Install Git Graph
This has the nicest "railway-track" display of commits that I have come across, although the dev seems to be not responding to contact during 2022.
An alternative is Git History, which remains under active development, although its railway-track display is less compact and efficient.
I am using vim plugin in VSCode. Sometimes, when I am in normal mode, I like to use my mouse to navigate, especially, if it is a big file. So I scroll to the new place, click there and try to begin editing my code by going back to the insert mode. However, when I use the insert mode, the cursor goes back to where it was before.
Vim cursor does not seem to remember the position of the new cursor updated on click. Is there any way to change this behaviour?
I have found a solution, downgrade from the latest v1.17.0 to the previous one.
To do so follow these steps:
Open extension navigation
Right click the Vim extension
Select "Install another version"
Click on 1.16.0
Fixed it for me. Hope this works for others that may have this issue.
I stumbled upon this thread on github.
As for the rest of the people having issues after version 1.17.0 there is now a new version 1.17.1 that might fix some of the issues you're facing.
So looks like it was a problem in version 1.17.0 but was fixed in the update 1.17.1
Just wondering if there is a way to get a tabbed view in VS Code (editor), and if not, is that feature yet to be added?
Update
Yes! VS Code 1.3.0 added this feature.
Original
Not as of v0.3.0, as far as I know.
Feature requests: http://visualstudio.uservoice.com/forums/293070-visual-studio-code
Issue reporting: https://code.visualstudio.com/Issues/List
Yes to both of your questions.
It recently became available, if you are on the nightly Insiders release. This will soon be introduced into the product itself as well, most likely in early July.
First, download the Insiders release.
In VS Code Insider's top application menu, open Preferences >
User Settings, and then add the following setting "workbench.editor.showTabs": true
You then will have tabs enabled in your editor as shown below
The closest thing to the tabs concept tha i found is using Ctrl+Tab to navigate in the history of opened files.
VS Code v1.3.0 has tabs similar to that of sublime text.
But Tab switching is still the same as the previous version.