/GitHub-Contribution-Graph

Procedural documentation for getting commits reflected in your GitHub profile Contribution Graph

UPDATE

We recommend against de-forking while in class - just so all the links submitted stay active. But, you don't really need to de-fork anything.

All the commit history lives in the .git folder in the local Git repo directory - you just need to get the project up to GitHub. This can be as simple as:

  1. creating a new repo on GitHub,
  2. giving it a unique name to help distinguish it in your GitHub repository list, and
  3. pushing the project up to the new GitHub repository.

It might help to make a "Team" to keep the "active student" repositories separate from the ones pushed up for the heatmap.

Lambda School's 2019 Git branching workflow will result in contributions reflected in your GitHub heatmap.

Latest update: 2/8/2019 :octocat:


THE FOLLOWING IS DEPRECATED

GitHub Contribution Graph

:octocat:

Heat Map

Please take a moment to review GitHub's "Learn How We Count Contributions" page. In particular the "Commit Was Made In A Fork" section. If you'd like all of your work to be reflected on your GitHub Contribution Graph, you can do the following:

"De-Forking" Your Project

  1. DO NOT DELETE YOUR LOCAL PROJECT!
  2. If you want your new and "non-forked" GitHub project name to match the old project name, first rename or delete your forked GitHub repository. Do this on GitHub. You can access the renaming and deleting options on GitHub in the "Settings" tab of your fork. Don't worry, if you delete your GitHub fork, your local copy will be safe.
  3. Create a new empty repository on GitHub. You are welcome to name it whatever makes sense to you. If you have renamed or deleted the old one, you can give it the same name of the original Lambda School project you are "de-forking" from.

Select "NEW repository" CREATE the new repository COPY the new repository's URL

  1. Add the new (and empty) GitHub repository as the "origin" remote to your local git repository.
$  git remote -v
   origin  https://github.com/LambdaSchool-PairStudentA/Preprocessing-I.git (fetch) <--- OLD ORIGIN URL
   origin  https://github.com/LambdaSchool-PairStudentA/Preprocessing-I.git (push) <---- OLD ORIGIN URL
                              ^^^^^^^^^^^^^^^^^^^^^^^^^
$  git remote set-url origin https://github.com/mixelpixel/Preprocessing-I.git <-------- SET NEW ORIGIN URL
$  git remote -v
   origin  https://github.com/mixelpixel/Preprocessing-I.git (fetch) <------------------ VERIFY NEW ORIGIN URL
   origin  https://github.com/mixelpixel/Preprocessing-I.git (push) >------------------- VERIFY NEW ORIGIN URL
                              ^^^^^^^^^^
  1. Push your local project to the new GitHub repository.
$  git push origin master
   Counting objects: 111, done.
   Delta compression using up to 4 threads.
   Compressing objects: 100% (77/77), done.
   Writing objects: 100% (111/111), 594.93 KiB | 45.76 MiB/s, done.
   Total 111 (delta 27), reused 111 (delta 27)
   remote: Resolving deltas: 100% (27/27), done.
   To https://github.com/mixelpixel/Preprocessing-I.git
   * [new branch]      master -> master

Local repository pushed to StudentB's NEW and NON-FORKED GitHub repository

BEFORE:

Previous contribution count

AFTER:

New and improved contribution count


How to RENAME your old GitHub Repo.

Rename your "OLD" repository

Go back to "De-Forking"


How to DELETE your old GitHub Repo.

  1. Select the "Settings" tab.

Select the SETTINGS tab

  1. Scroll down to "The Danger Zone."

SCROLL down to the DANGER ZONE

  1. Press the red button!

DELETE this repository

☝️ Click ☝️ on ☝️ this ☝️ picture ☝️ before you enter "The Danger Zone" 👍

  1. Confirm you are not a robot and press the BIG RED BUTTON!

Enter the PROJECT name and press the BIG RED BUTTON

Go back to "De-Forking"

:octocat: