Shulou(Shulou.com)06/02 Report--

Github contribbution does not record what to do. In response to this problem, this article introduces the corresponding analysis and answers in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

Preface

Partners who have been using GitHub managed code for a long time may find that they sometimes write the code for a few days, but find contribbution (the small green box is not lit)

So what kind of commit will be counted? here we find the answer from github help. You can take a look at those who are good at English.

Chinese

Issues and pull requests

This operation is within a year.

This operation is for a separate warehouse, not fork.

Commits your commits is displayed when it meets the following conditions:

Note: the contribution of a private library is shown only to private library members

You are a collaborator of this warehouse, or a member of the owning organization of this version library.

You fork this warehouse.

Have you initiated pull request or issue against this warehouse?

You marked the warehouse with Star.

On the default branch (usually master)

In the gh-pages branch (warehouse containing Project Pages sites)

Commits submitted within one year

The email address used by commits is associated with your Github account

These commits are in a separate warehouse rather than an fork warehouse (bloggers made such an error that the commit was not recorded for half a month before discovering it)

These commits are in:

In addition, at least one of the following conditions is met (the warehouse mainly aimed at your Commit is not created by you):

Several common reasons why Contributions is not included in Github * users who are doing Commits are not associated with your Github account. * Commit is not done in the default branch of this version library. * this warehouse is a Fork warehouse, not a stand-alone warehouse. (this is the kind of error made by bloggers) how to troubleshoot whether you can use the command `git log` in your local repo to check whether the personal mailbox on the `room` record is correct. For example, it is because the user name is not configured after switching to the Mac platform before development, so the mailbox on my subsequent commit record has always been mrchang, so Github will think that you did not submit these commits! Remedial measures

However, there is no remedy for this. The detailed remedial process is given on the Github website. Students who are good at English should move to Changing author info by themselves. Here are the brief steps I translated from Github Help:

Change author information

Warning: this behavior can be destructive to your repo history. If your repo works with others, it's a bad habit to rewrite published history. Perform this operation only in an emergency. Using a script to change the Git history of your repo we have written a script that changes the old email address of the commit author to the correct user name and email address.

To change the existing user name and / or email address of commits, you must rewrite the entire history of your Git repo.

Use scripts to change the Git history of a repo

We have created a script that will correct all the author information in commits and the old user name and email address in the submitter field after you submit with the correct name and email address.

Note: executing this script will rewrite the history of all repo collaborators. After doing the following, anyone in fork or clone must get the rewritten history and put all local modifications rebase into the rewritten history.

The information you need to prepare before executing this script:

Open command prompt (command prompt) under Mac and Linux under Terminal,Windows

Create a brand new clone for your repo

Git clone-- bare https://github.com/user/repo.git

Cd repo.git

Copy and paste the script and modify the following variables according to your information: old Email address, correct user name, correct email address

`#! / bin/sh git filter-branch-- env-filter 'OLD_EMAIL= "Old Email address" CORRECT_NAME= "correct user name" CORRECT_EMAIL= "correct email address" if ["$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL"] then export GIT_COMMITTER_NAME= "$CORRECT_NAME" export GIT_COMMITTER_EMAIL= " $CORRECT_EMAIL "fi if [" $GIT_AUTHOR_EMAIL "=" $OLD_EMAIL "] then export GIT_AUTHOR_NAME=" $CORRECT_NAME "export GIT_AUTHOR_EMAIL=" $CORRECT_EMAIL "fi'- tag-name-filter cat-branches-- tags`

Press Enter to execute the script.

Use the git log command to see if there are any errors in the new Git history

Push the correct history to Github

Git push-force-tags origin 'refs/heads/*'

Delete the clone you just created temporarily

Cd..

Rm-rf repo.git

How to set your git personal information correctly

Next, set up your correct information globally, and then rest assured to use Github for version management.

Git config-global user.email "your email address"

Git config-global user.name "your Github user name"

The answer to the question about what to do without a record in github contribbution is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.