Access to someone else's repository GitHub
I can't change the guita repository. The repository itself is successfully cloned. But after the comet and the team
git pushThe following remotes appear:
Permission to %The full name of the repository% denied to % My logic on GitHub%.
The SSH key was successfully created and also successfully connected to my GitHub account. Such a mistake arises both in the console tuche and in sync in the disktop annex GiHub. At the same time, the repository owner calmly makes various rights.
How's the trouble going?
If there is a lack of access rights, how to extradite them (by the owner of the repository)
carriann last edited by
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.
- 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.