Always use the "git" userĪll connections, including those for remote URLs, must be made as the "git" user. The connection should be made on port 22, unless you're overriding settings to use SSH over HTTPS. To make sure you are connecting to the right domain, you can enter the following command: $ ssh -vT > OpenSSH_8.1p1, LibreSSL 2.7.3 > debug1: Reading configuration data /Users/YOU/.ssh/config > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 47: Applying options for * > debug1: Connecting to port 22. In some cases, a corporate network may cause issues resolving the DNS record as well. Pay attention to what you type you won't be able to connect to "" or "". Check that you are connecting to the correct server If you generate SSH keys without sudo and then try to use a command like sudo git push, you won't be using the same keys that you generated. If you have a very good reason you must use sudo, then ensure you are using it with every command (it's probably just better to use su to get a shell as root at that point).
You should not be using the sudo command or elevated privileges, such as administrator permissions, with Git.
Use -rebase-merges instead of -p ( -p is deprecated and has serious issues).Should the sudo command or elevated privileges be used with Git?
GITKRAKEN PUSH FAILED ACCESS DENIED UPDATE
Update for modern git clients (July 2020) For the case where you're just changing the most recent commit, this is not an issue. The manpage for git rebase warns that using -p and -i can lead to issues, but in the BUGS section it says "Editing commits and rewording their commit messages should work fine." The solution is to use the -p flag to git rebase, which will preserve the merge structure of your history. This can very often lead to a very different history (as duplicate changes may be "rebased out"), and in the worst case, it can lead to git rebase asking you to resolve difficult merge conflicts (which were likely already resolved in the merge commits). If there are any merge commits between the current HEAD and your, then git rebase will flatten them (and by the way, if you use GitHub pull requests, there are going to be a ton of merge commits in your history). There was a slight flaw in my original response. If you want to set the committer to something you specify, this will set both the author and the committer: git -c user.name="New Author Name" -c commit -amend -reset-author This will change the author to the name specified, but the committer will be set to your configured user in git config user.name and git config user.email. Just do git commit -amend -author "New Author Name " So that the command will be: git commit -amend -author "New Author Name " -no-edit & \Īs some of the commenters have noted, if you just want to change the most recent commit, the rebase command is not necessary. You could skip opening the editor altogether here by appending -no-edit Then, when git asks you to amend each commit, do git commit -amend -author "New Author Name "Įdit or just close the editor that opens, and then do git rebase -continue If you also want to change your first commit, you have to manually add it as the first line in the rebase file (follow the format of the other lines). Then mark all of your bad commits as "edit" in the rebase file. If you only want to fix the spelling of a name or update an old email, git lets you do this without rewriting history using. NOTE: This answer changes SHA1s, so take care when using it on a branch that has already been pushed. $ git remote add win32 git:///users/joe/myproject-win32-portĪt this point, things are getting pretty crazy, so run gitk to see what's going on: $ gitk -all & You can actually track more than one remote repository using git remote. Now, if you look at your local branches, this is what you'll see: $ git branch As the previous line tells you, the branch is being set up to track the remote branch, which usually means the origin/branch_name branch. Here, "new branch" simply means that the branch is taken from the index and created locally for you. If you just want to take a quick peek at an upstream branch, you can check it out directly: $ git checkout origin/experimentalīut if you want to work on that branch, you'll need to create a local tracking branch which is done automatically by: $ git checkout experimentalĪnd you will see Branch experimental set up to track remote branch experimental from origin. Next, look at the local branches in your repository: $ git branchīut there are other branches hiding in your repository! You can see these using the -a flag: $ git branch -a First, clone a remote Git repository and cd into it: $ git clone git:///myproject
0 kommentar(er)
