If I understood the question correctly. Start pulling, localize all conflicts, and only after that do push.

Judging by handing over the request https://www.google.ru/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=github%20create%20repository%20from%20local You can use API guithab and send a request for a cut to create a repository as described https://stackoverflow.com/a/10325316/3212712 curl -u 'USER' https://api.github.com/user/repos -d '{"name":"REPO"}' Replace. USER To your lasernam a REPO in the name of a new repository. Once this request is sent, you will have to introduce the password from the account and the repositories will be created.After which a new one can be added remote For local repository and scare everything you need:git remote add origin git@github.com:USER/REPO.git git push origin master

error: src refspec Tim_Musharapov does not match anyIt means there's just no branch in the repository. Tim_Musharapov♪ It needs to be created. Such syntaxis shall be used to create winds: git push origin что:куда Here. что - it's a local branch you want to scare, and куда - the name of the new branch of origin that you want to scare into. что♪ A origin This is the name of the deleted repository (remote), it may be different, but it is used by default.Therefore, the next option git push origin master:Tim_Musharapov means "take a local branch master and intimidate the newly created branch Tim_Musharapov" It's working, but there's an inconsistency in the names of local and remote branches. And the branch. master You've got your own job now, and it's embarrassing to get an update of the branch. master Repository origin:Your branch is ahead of 'origin/master' by 3 commitsIn your branch. master There are three of your commites, so... git pull I can't get into this branch.There is a common practice: to call local and removed branches the same. It's not necessary (i.e. Git allows to do differently), but it's convenient and practical. So if you can't change the removed branch master do not alter the progress of work into the local area master♪ I therefore propose such a solution:First of all, we need a branch in which we will share the results of our work. She might be called, like, Tim_Musharapovbut https://ru.stackoverflow.com/a/573773/181472 Not by the name of the developer.If there's no such branch yet, it needs to be built to duplicate it. master (laughing on the same comemite).git checkout -b Tim_Musharapov master If there is a branch, we'll update it to the current master:git checkout Tim_Musharapov git merge --ff-only master # если конфликт, значит там есть какие-то изменения, которых нет в master # нужно смотреть и разбираться. Put her in origin, key. -u Maintains the local and removed gridgit push -u origin Tim_Musharapov:Tim_Musharapov в следующий раз из этой ветки можно будет пушить проще: git push And the master branch https://ru.stackoverflow.com/q/431520/181472 git checkout master git reset --hard origin/master В локальную ветку master мы будем получать обновления с origin git checkout master git pull A little more about synthaxis. что:куда:git checkout somebranch Оба варианта создают одноимённую ветку на origin git push origin -u somebranch git push origin -u somebranch: Запушить "ничего" в ветку - значит удалить её git push origin :otherbranch

I solved the problem with the team:git branch --set-upstream-to=origin/master Thank you, everyone.

The comite needs to be re-routed by the team. https://git-scm.com/docs/git-revert It's ideologically wrong to roll off a comem sent to a remote repository because someone with this commite can pick up, work with him, and not be thrilled that he suddenly disappears.But if the problem isn't that you've poured a comic code, and the fact that you're keeping some passwords in the river, and now you've put them on the guithab, you can drop the commit with help.git reset --hard and send them to the remote river for some reason.git push -f origin master But it's an emergency.

git clone --bare git@git.test.com:my-repo-a.git git fetch origin git remote add new-origin git@git.test.com:my-repo-b.git git push --mirror new-origin git remote rm origin git remote rename new-origin origin Source: https://www.smashingmagazine.com/2014/05/moving-git-repository-new-server/ Updated: corrected comments

The bay is located at an address that is listed in the bay. remote each local repository. When you clone repositories from a remote server (Github or Bitbucket), the repository is installed remote by name origin where the address is indicated. Privacy git push origin The files/changes will be sent to the remote repository with the address.There's nothing to limit you to change and adding others. remote- Oh. I mean, you can lean with Github, change your back. remote and blow on Bitbucket. Or vice versa. You can add one. remote for a staircase and torch and in Github and Bitbucket.

GitHub makes it easy to make forks of other people's repositories. Do a copy of the library to yourself and use it as a submodule.

on server:Catalogue /путь/к/ Do the team:$ git config receive.denyCurrentBranch ignore inpository/путь/к/.git/Create. /путь/к/.git/hooks/post-update to read:#!/bin/sh GIT_WORK_TREE=$(dirname $PWD) git reset --hard $(git rev-parse $1) Add this bat:$ chmod +x /путь/к/.git/hooks/post-update Everything.Now you can clone this vault locally:$ git clone пользователь@сервер:/путь/к/ add files, branches, make up and send changes to the team server git push (I understand that if there are no branches on the server, it will have to be indicated, for example: git push origin ветка)If you need to switch to another comedian/light without creating a new commit, then you'll have to do it on the server. /путь/к/) git checkout -f ... or git reset --hard ...On the one hand, these questions (and their responses) should simplify the process: https://ru.stackoverflow.com/q/428483/178576 https://stackoverflow.com/q/279169/4827341

$ git remote show origin ... Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) I can see that for the team. git pull (without parameters) only localized branch master (becomes to get an update from the remote branch) masteralso for git push (without parameters) - only updates from the local grid master They'll go to a remote repository. master)The local branch can be configured to send changes to any branch of the remote repository (on call) git push No parameters in this branch.It's the best thing to do, once you turn the team. git push Opium -u (sighs)--set-upstreamNaturally, the name and the branch of the repository, to which the current branch will be " tied " , should be indicated.for your specific case:Make a branch. develop current:$ git checkout develop send a change from it, pointing out the " link " to the removed branch. develop Repository origin (example of conclusion):$ git push -u origin develop Total 0 (delta 0), reused 0 (delta 0) To url-репозитория * [new branch] develop -> develop Branch develop set up to track remote branch develop from origin. The last line reports that the local branch develop " tied " to the removed branch develop (repository) origin)Now team:$ git remote show origin Show a little more information on the links:... Local branches configured for 'git pull': develop merges with remote develop master merges with remote master Local refs configured for 'git push': develop pushes to develop (up to date) master pushes to master (up to date) continued in the branch develop team git push (without parameters) sends the changes exactly to the develop♪by wordBy sending changes from any local branch into (almost) any branch in a remote repository (and without any " connections " ) it is possible to:$ git push репозиторий локальная_ветка:удалённая_ветка For example, in your case:$ git push origin develop:develop If a branch with the said name does not exist in a remote repository, it will be established, and if there is, in principle, the team may end with a mistake - if " change from the local branch to the remote will not be possible, but this is a very different story.

The second option clearly shows where you put the comedian, the first one is invisible.In most cases, it is sufficient to indicate the first option, in the last case, you will have a type of note (git 2.0 - 2.8):[ak@server abc]$ git push warning: push.default is unset; its implicit value is changing in Git 2.0 from 'matching' to 'simple'. To squelch this message and maintain the current behavior after the default changes, use: git config --global push.default matching To squelch this message and adopt the new behavior now, use: git config --global push.default simple See 'git help config' and search for 'push.default' for further information. (the 'simple' mode was introduced in Git 1.7.11. Use the similar mode 'current' instead of 'simple' if you sometimes use older versions of Git) Counting objects: 5, done. Delta compression using up to 2 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 367 bytes | 0 bytes/s, done. Total 3 (delta 2), reused 0 (delta 0) To abc@asdf:/asdfasddf.git b41acb4..b8c32bd master -> master https://habrahabr.ru/post/225251/ :One of the most important changes is team git push. Now, in default (if no wind is specified), push will be carried out Only the current branch. Git 1.* default pushing all branches, which were localized. Of course you can go back to the end. conduct, this is the opportunity push.default.It's very popular. https://stackoverflow.com/questions/13148066/ It says the same thing:matching Which means git push sends all your local branches in the same remote server.simple Which means git push It'll only send the current branch in the same remote server.Simple is a more intuitive regime, so it is default push.default not established.

And now I want to scare her into a local branch developYou can't scare one local branch into another. Only a remote server can intimidate. And you probably want to swap two branches together. It's called merge. I don't know what to do with this idea, I do it, and I strongly recommend it, in consoles. It's just there.git checkout develop # перешли в develop git merge featureRefactorCameraHelper # слили featureRefactorCameraHelper -> origin:+featureRefactorCameraHelperIt's not a tricky environment that shows that your branch featureRefactorCameraHelper I'll be sent to the pseudonym server. origin (is a default name for a remote server). And the plus one means that this branch will be created if it's not there.

You came to Git with SVN habits.Git is a distributed version management system. It means that, by default, everyone is a VP in their repository, but a puzzle in someone else. When you cloned repositories, you had a full copy of the repository on your computer, in which you can create branches where you can extract changes from other people's repositories and so on. But the repository at the owner's own, separate, and your dirty pets don't have to go there. If the owner decides to give you yellow pants and the right to access your repository, then you can do whatever you want. But there's not enough C.In general, the picture is: the owner has repositories on the guitaba and is likely to have at least one local repository on his computer. From Git's point of view, you have enough to clone his remote repositories, make changes, throw their repositories, and then share these changes with the owner in a convenient way. For example, if you make your repository publicly available, the owner can make a pool of your repository and change. Or you can send the changes by mail.GitHub is a little more comfortable, with all the gooes and all the other fenes, but it needs to be done. You push someone else's repositories on your account, clone on your computer, create a branch, make changes, put in a local repository, throw a local branch in your repositories on the guithab, create a pool revegetation, take care of your poulle-revet.Important points:You always work with your repositories, you only tell the owner that you have something useful.Always create separate branches under each separate set of changes. Pulle Revest works through branches. If the owner asks to fix something, you can add changes to the same branch within one pool revest.If you work actively on the project, and the owner trusts you to change your own repositories, the pool revest will become unnecessary. But if you don't know Git, don't count on it.Minor trivial changes can be made within the framework of their remote repository on guithab without the creation of a local repository. Githab lets edit the file even in someone's repository, but you'll still get a fork with a branch on your own account.

Remove several local branches:$ git branch -d ветка1 ветка2 ... Deleted branch ветка1 (was 6bb54a3). Deleted branch ветка2 (was 6bb54a3). ... Reposit a few branches origin:$ git push origin :ветка1 :ветка2 ... To ... - [deleted] ветка1 - [deleted] ветка2 ...

I see two different questions:Like one branch to replicate:# переключаемся на ту, куда копировать git checkout master # объединяем с той, из которой копируем git merge test-develop # если будут конфликты, правим их руками, а потом git add . git merge --continue How a github# убеждаемся, что удалённый репозиторий вообще настроен git remote -v переходим в нужную ветку и убеждаемся, что она не расходится с удаленным репозиторием git checkout test-develop git pull #тут могут быть конфликты пушим текущую ветку в новую удалённую и одновременно назначаем соответствие git push -u origin test-develop: в следующий раз можем пушить без указания подробностей git checkout test-develop git pull git push можем запушить все локальные ветки сразу git push --all

Hello.I ran into the same problem, it didn't work out in the forehead, so I used the roundabout. If still relevant to you, this is the solution:To make the Push, you need repositories on a remote server (e.g. GitHub). The repository is a folder of your project. The repositories on the server may be a lot (under each project their folder). Put the file on your GitHub.com project. Immediately after the repository on GitHub (e.g.) You will see the following message inside your repository: ...or create a new repository on the command lineecho "# ProgrammingInLinuxBook" >> README.md git init git add README.md git commit -m "first commit" git remote add origin https://github.com/имяПользователя/названиеРепозитория.git git push -u origin master We'll use these teams. )Go on, get in the file of yourI work with Linux and I have Git installed. Either way, you need to set up Git.If you have Linux, go into the folder of the project and open the Terminal (right button of mouse at an empty place -- Open in Terminal)If you have Windows, open the terminal (or whatever's in it with Git) and go to the folder of the draft by CD teams. ♪ ♪Next, put the team in Terminal:echo "# НазваниеПапкиВашегоПроекта" >> README.mdThe title of the project folder should be the same as the name of the GitHub repository.Next, put the team in Terminal: git initNext, put the team in Terminal: git add README.mdNext, put the team in Terminal: git commit -m "first commit"Next, put the team in Terminal: git remote add origin https://github.com/имяПользователя/названиеРепозитория.git Next, put the team in Terminal: git push -u origin masterThat's it. Now open up GitKraken, there's a needle on the left in the sight of the cloud, there'll be your remote repository. Try pushing the Push button now.

You know, before you're big, git commit and beating. git push The change must be on the old computer. git pull The repository changesitory to itself, now the content of the remote and local repository(s)atters.This option would, by the way, be appropriate if there was a situation that, at some point, the old computer had simply stopped making changes and all work was done with another computer.

team (produced and exemplified)$ git branch -r origin/ветка1 origin/ветка2 repo2/ветка3 repo3/ветка4 Show all branches to your local repository of remote repositories.The repositories appear under the (authorised) names under which they are connected. origin♪ repo2 and repo3♪Name origin - by default, a remote repository, e.g. when performed git clone♪In principle, in order to send changes from the current branch to any of the branches of any of the repositories connected, it may be possible to:$ git push имя-репозитория имя-ветки for the example given above to send changes, for example origin/ветка2, you can:$ git push origin ветка2 but send changes arbitrary local branch Arbitrary It's probably not gonna work out, and you can get a mistake in the species:error: src refspec branch2 does not match anyThat's what makes it clear. Source..this may be the name of the local branch, the xash of a committ or mark (including " special " ) HEADwhich points to the current commit where your work copy of the repository is switched.$ git push имя-репозитория источник:ветка But it's not a victory, but it's probably just that you can get in response to a mistake in the species:To url repository?error: failed to push some refs to 'url-repository'hint: Updates were rejected because a pushed branch tip is behind its remotehint: counterpart. Check out this branch and merge the remote changeshint: (e.g. 'git pull') before pushing again.hint: See the 'Note about fast-forwards' in 'git push --help' for details.It means that your current comedian cannot connect a chain of comemites to a commite that is marked by a remote branch. git - it's just a flame marker.And you had to do something different.For example:Establish a local branch based on the remote and switch to:$ git checkout -b ветка2 origin/ветка2 make the necessary changes, make the necessary rooms.send these changes to the remote repository:$ git push

For each remote repository, you can ask pushurl, i.e., urlwhich will be subject to command changes push♪this one. pushurlby the way, maybe not a match. url this repository, that's the trick: pushI think it's a repository. bitbucket- and the changes go. github♪moreover: pushurl- there may be more than one, and change of one team will be on multiple occasions. url- Mm.Added pushurl with a team of approximately this:$ git remote set-url --add --push имя-репозитория url-репозитория From theory to practice.create three (for sure) bare repository:$ for i in 1 2 3; do git init --bare repo$i; done Initialized empty Git repository in ./repo1/ Initialized empty Git repository in ./repo2/ Initialized empty Git repository in ./repo3/ And make the clone of the first one:$ git clone repo1 work Cloning into 'work'... warning: You appear to have cloned an empty repository. done. $ cd work Let's see the default configuration remote-So:$ git config --get-regexp "^remote" remote.origin.url ../repo1 remote.origin.fetch +refs/heads/*:refs/remotes/origin/* And now we'll add pushurl- for all bare repositories established, without forgetting the original repository itself.../repo1$ for i in 1 2 3; do git remote set-url --add --push origin ../repo$i; done $ git config --get-regexp "^remote" remote.origin.url ../repo1 remote.origin.fetch +refs/heads/*:refs/remotes/origin/* remote.origin.pushurl ../repo1 remote.origin.pushurl ../repo2 remote.origin.pushurl ../repo3 As you can see, pushurl- You're positively added.Let's make a comemite and send it to the team. push:$ date > file $ git add file $ git commit -m 1 [master (root-commit) 2d68407] 1 1 file changed, 1 insertion(+) create mode 100644 file $ git push Counting objects: 3, done. Writing objects: 100% (3/3), 228 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ../repo1 * [new branch] master -> master Counting objects: 3, done. Writing objects: 100% (3/3), 228 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ../repo2 * [new branch] master -> master Counting objects: 3, done. Writing objects: 100% (3/3), 228 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ../repo3 * [new branch] master -> master The committ went to all three bare repository by one team!What about the other branches?Let's make another branch.newWe'll add a committ and send a change:$ git checkout -b new Switched to a new branch 'new' $ date >> file $ git commit -am 2 [new c82bfe5] 2 1 file changed, 1 insertion(+) $ git push -u origin new Counting objects: 3, done. Writing objects: 100% (3/3), 264 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ../repo1 * [new branch] new -> new Branch new set up to track remote branch new from origin. Counting objects: 3, done. Writing objects: 100% (3/3), 264 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ../repo2 * [new branch] new -> new Branch new set up to track remote branch new from origin. Counting objects: 3, done. Writing objects: 100% (3/3), 264 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) To ../repo3 * [new branch] new -> new Branch new set up to track remote branch new from origin. This magia works with new branches! new All three bare repositories.response based on information https://stackoverflow.com/a/14290145/4827341 and https://stackoverflow.com/a/3195446/4827341 Answers.

when you did git initYou already. created local repositories. .git♪The files you created in this catalogue./path/to/my/project/and then by git add and git commit " Added to repositories " are in fact only working copy The contents of the repository.repository may be free of work copiescreates such a repository when using the opposition --bare teams git clone♪ git init..you actually get the same contents in this repository as in the catalogue. .git Repository with work copy♪to create still. One local copy of the repository, as you did in the catalogue. /path/to/git/repo/all the contents of the repository, all the commites, the whole story, are available in any of the git repository and free access to the Internet, and the committs to this copy of the repository you can make. free Internet access.And how to make a second (third, tenth) copy of the repository on some remote server, you already know:$ git remote add ... $ git push ... As a team git push send changes straight to several repositories, written for example https://stackoverflow.com/a/14290145/4827341 and https://stackoverflow.com/a/3195446/4827341 and Russian: https://ru.stackoverflow.com/q/499738/178576