I can not make changes to the gita repository. The repository itself has been successfully cloned. But after making a commit and a git push command, the following remote appears:

Permission to% The full name of the repository is% denied to% My login on GitHub%.

The SSH key was successfully created and also successfully connected to my GitHub account. This error occurs both with the console "push" and during synchronization in the desktop application GiHub. With this, the owner of the repository calmly makes various edits.

How is trouble solved?

If the matter is lack of access rights, then how to issue them (from the repository owner)

  • 3
    by creating a fork and (if necessary) sending pull requests . - aleksandr barakin
  • Those. there are no other options? Do you have to always create forks and send pull requests? Parallel branches cannot be created either, because adding a new branch has the same error. @alexanderbarakin - Jereli
  • 3
    Ask the owner to contribute you to the Collaborators ( help.github.com/articles/… ) - Vladimir Gamalyan
  • 2
    Well, you are interested in the capabilities of the specific site (github.com), and not “for life at all”. if “in general for life”, then patches can be sent by mail ( git-scm.com/docs/git-format-patch ). - aleksandr barakin

1 answer 1

You came to Git with habits from SVN.

Git is a distributed version control system. This means that by default everyone is a prostate in his repository, but patsak is in someone else's. When you cloned a repository, then you had a full copy of the repository on your computer, in which you can create branches, in which you can pull changes from other repositories, and so on. But the repository of the owner is his own, separate, and there is no need to climb there with his dirty Patzak hands. If the owner decides to give you yellow pants and rights to access your repository - then you can already do what you want. But while KC is not enough.

In general, the picture is this: the owner has a repository on the githaba and, most likely, at least one local repository on his computer. From the point of view of Git, you just need to clone its remote repository, make changes, push them to your repository, and then share these changes with the owner in a way that is convenient for you. For example, if you make your repository publicly available, the owner can make a pull from your repository and merge the changes. Or you can send the changes by mail.

As part of GitHub, everything is somewhat more convenient, with all sorts of pull-requests in Guy and other baubles, but for everything to work, you need to follow the procedure. You fork a foreign repository into your account, clone your computer, create a branch, make changes, push to a local repository, push a local branch to your repository on the githabe, create a pull-request through the githaba interface, the owner sees your pull-request, your bullet change, and then it is his concern.

Important points:

  1. You always work with your repositories, you only inform the owner that you have something useful.
  2. Always create separate branches for each separate set of changes. Pull-requests work through branches. If the owner asks to fix something, then you can add changes to the same branch within a single pull request.
  3. If you actively work on the project, and the owner entrusts you to independently make changes to his repository, then pull-requests will become unnecessary. But if you don’t know Git, don’t count on it.
  4. Minor trivial changes can be made as part of your remote repository on the githaba without creating a local repository. Github allows you to "edit" the file, even in someone else's repository, but you still get a fork with a branch on your account.
  • four
    The explanation through Kin-Dza-Dza pleased. ) - Nick Volynkin ♦