git-extensions

Can't authenticate to GitHub from Git Extensions?

浪子不回头ぞ 提交于 2019-12-04 05:24:25
I'm just setting up Git Extensions in Visual Studio 2010 and can't really get it to work - I can't authenticate. In Git Extensions, if I choose Plugins->GitHub I can add user, password, API token and choose SSH. Fine. Except that API tokens aren't available anymore as GitHub are moving to API v 3 now. Anyone got news on this? I've seen a very recent discussion but no clue. Surely there must be more GitHub users than me using Git Extensions and having authentication issues? Just for future reference: this has been fixed since v2.33 来源: https://stackoverflow.com/questions/10341662/cant

Can't manage to load my private key with git extension

好久不见. 提交于 2019-12-04 02:55:04
I've been trying for the last 2 hours. I'm using xp-dev as a git repository provider (because I'm already paying and I have svn repo over there) I've given xp-dev my public key. But when cloning my repo I a being rejected. "C:\Program Files (x86)\Git\bin\git.exe" clone -v --recurse-submodules --progress "ssh://xp-dev.com/repogit" "c:/ProjetPerso/repogit" Cloning into 'c:/ProjetPerso/repogit'... Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Done And from what I understood from various

Personal vs central repositories

前提是你 提交于 2019-12-03 20:10:30
问题 I am trying to set up version control software, currently I work alone (but I expect that to change), and I want to store the code on a network drive which is regularly backed up but work off the same code on my laptop's hard drive. But GIT is confusing me greatly! So from what I can understand, I should create a personal repository on my laptop, and then either push or clone this to a new central repository on the network drive. Does this sounds correct? Is this done by pushing or cloning? I

The fingerprint of this host is not registered by PuTTY?

天涯浪子 提交于 2019-12-03 13:47:12
I'm a quite beginner in using Git (cmd, and UI clients), I installed Git extensions, set up all requirements. When I tried to connect to a repository on BitBucket, private account (I used my own ppk that I have on my computer), I get this message: When I click on Yes I'm presented with a Git window: Can anyone help me get over this so I can clone repositories? Open the command prompt or Git bash and run the following command, where the bracketed term is the username and SSH path of your BitBucket repository: plink [git@bitbucket.org:company/repo-name.git] If "plink" is an unrecognized command,

How to remove/hide GitExtensions toolbar from Visual Studio?

别说谁变了你拦得住时间么 提交于 2019-12-03 11:36:02
问题 I tried: right-click on a toolbar and uncheck GitExtensions right-click on a toolbar > Customize and delete GitExtensions moved the toolbar from the second row to the first row searched GitExtensions settings for a way to disable/hide the toolbar, but didn't find anything The GitExtensions toolbar shows up again on the second toolbar row after a computer restart. I use: Windows 8 Visual Studio 2012 Git 1.7.11 GitExtensions 2.41 回答1: The Git Extension files are stored in your 'My Documents'

How to remove/hide GitExtensions toolbar from Visual Studio?

可紊 提交于 2019-12-03 01:10:00
I tried: right-click on a toolbar and uncheck GitExtensions right-click on a toolbar > Customize and delete GitExtensions moved the toolbar from the second row to the first row searched GitExtensions settings for a way to disable/hide the toolbar, but didn't find anything The GitExtensions toolbar shows up again on the second toolbar row after a computer restart. I use: Windows 8 Visual Studio 2012 Git 1.7.11 GitExtensions 2.41 The Git Extension files are stored in your 'My Documents' folder in a "Visual Studio 2012" subfolder. Removing these files will make the toolbar disappear from within

How can I specify which branch should be checked out in a fresh clone?

只谈情不闲聊 提交于 2019-12-02 16:11:37
问题 In Git Extensions, the user can, when cloning a repository, specify which branch (possibly other than master ) should be checked out in the resulting clone. How can I do that at the command line? 回答1: The answer, as often, is in the man pages (in the git-clone man page, here): --branch <name>, -b <name> Instead of pointing the newly created HEAD to the branch pointed to by the cloned repository's HEAD, point to <name> branch instead. In a non-bare repository, this is the branch that will be

TortoiseGit vs Git Extensions

蓝咒 提交于 2019-12-02 15:41:58
What are the benefits and disadvantage of using either Git Extensions or TortoiseGit on a Windows Based OS? Rafael Ibraim I don't know GitExtensions, but I can share my experience with TortoiseGit (alluded to by marc_s's comment): Pros: Excellent integration with Windows (it's a shell extension) Nearly the same UI as TortoiseSVN (if you already used TortoiseSVN, you know what to expect). Cons: You will have a hard time understanding how to use git. The problem with TortoiseGit is that people who worked with TortoiseSVN will think everything will (or should) work exactly like in SVN... and end

How can I specify which branch should be checked out in a fresh clone?

天大地大妈咪最大 提交于 2019-12-02 09:06:24
In Git Extensions, the user can, when cloning a repository, specify which branch (possibly other than master ) should be checked out in the resulting clone. How can I do that at the command line? jub0bs The answer, as often, is in the man pages (in the git-clone man page, here): --branch <name>, -b <name> Instead of pointing the newly created HEAD to the branch pointed to by the cloned repository's HEAD, point to <name> branch instead. In a non-bare repository, this is the branch that will be checked out. --branch can also take tags and detaches the HEAD at that commit in the resulting

GitExtensions + Putty via SSH on custom port

醉酒当歌 提交于 2019-12-01 17:39:18
I have a git repository that I pull using a path similar to this: git pull ssh://username@host.com:1234/path/to/repository.git When GitExtensions then tries to pull from the repo using plink, it makes this call: plink -T username@host.com:/path/to/repository.git This ends up failing because it's actually pinging port #22, and not #1234. The right call to make would be plink -T -P 1234 username@host.com:/path/to/repository.git If I create an alias "hostCom" in my ~/.ssh/config, it seems to work correctly (connecting to #1234) if I just do this: plink -T username@hostCom But as soon as I add the