This might be related to a limit on Github's end that the contributions history is limited only to the last 1000 commits in case of a larger number of commits are pushed in a single push. (I discovered and mention it the PS section while tinkering some time back).
If that is what is happening in your case, i.e., by importing a repo you mean you're pushing your bitbucket code into a fresh repo in github manually using git push github master
, you may want to break down your pushes into small batches. Create a tag every 1000 commits or so from the initial commit, and push these tags in chronological order.
The setting git config user.email "email@example.com"
is used only when new commits are being created, so it doesn't have any affect here other than that your future commits will show in contribution history.
Also, as mentioned on github.com articles, ensure that:
Commits will appear on your contributions graph if they meet all of
the following conditions:
- The email address used for the commits is associated with your GitHub
account.
- The commits were made in a standalone repository, not a fork.
- The commits were made:
a) In the repository's default branch, usually master
b) In the gh-pages branch for repositories with Project Pages sites