September 9, 2014 at 11:55

How to attract world stars of programming into your project or an interesting feature of GitHub

Relatively recently, I had to use the Git system a bit more complicated than the banal click in the Android Studio button on the commit button. Today, by my own indiscretion, I found an interesting feature of the Git GUI: if you enter the e-mail of any GitHub user in the client’s settings, but when you push (commit) the commit (commit), enter your data, then looking at the site in the commit section you can see something strange. The commit will not be executed on behalf of you, but on behalf of the person who is entered in the Git GUI settings. This will be more clearly seen in the attached video with step-by-step actions:



Without hesitation, I decided to turn to a more experienced colleague for clarification. After ten minutes of samples with brute force e-mail, a joint decision was made to write to those. support, but the answer from GitHub surprised no less:

Hi,

Because git is a distributed version controls system GitHub must use the commit email address to assign attribution. When you push a repository to GitHub.com it may contains one or more commits, some of which you may not have authored. For example, imagine a scenario where you collaborated with a number of people on a git repository before you made your first push of that repo to GitHub.com. This push would contain a number of commits from several authors. It would be incorrect to assign all of the commits to the person doing the push, so we use the commit log email addresses to assign attribution on GitHub.com. Each subsequent push to GitHub uses this same logic to assign attribution of commit authors.

Thanks!
Patrick


It turns out that GitHub does not consider it a bug that virtually anyone can make commits on behalf of another developer. Well, now the best programmers in the world will help me fix bugs.
Tags:

Also popular now: