Blackbelt Sourcing on Github

Are you a sourcer or recruiter looking for talent on Github?

Are you a marketer looking for prospects on Github?

Learn more about sourcing on Github…

What is Github?

Github comes from Git + hub.

Git is a version control system for software development.

A comparison is Google Docs. If you are familiar with Google Docs you know that you can recover a previous version of a file.

If you are not familiar with Google Docs versioning, perhaps you are familiar with Sharing an Excel file. You make changes, someone else makes changes and so on. But what if one day someone makes a change and deletes some of your work? End of the world right?

What if you could recover a previous version of that Excel file? That would be like discovering fire right?

In software development we have a similar scenario. A lot of developers contribute to a project by writing a piece of code.

Git, also known as “version control” allows the project owner to revert to a previous version if necessary.

Git was created in 2005 by Linus Torvalds, the creator of Linux.

Github is not owned by Linus. Github is an independent company that wanted to create Git as software as a service. Github was launched in 2008 and was built in Ruby. It has around 15M users.

The Anatomy of Github

I encourage you to open a Github account. Even if you are not a developer. To get an idea of what the product is about. Although you won’t make much sense of it unless you create your own repository.

A repository is a project.

There are public and private repositories.

Most open source projects have a public repository that you can look at. For example this one:


Just click around to see what is inside every menu and you will discover a lot of useful information.

Common Sourcing Pitfalls

You shouldn’t evaluate a developer by the number of green rectangles they have on their contributor bar.

If you don’t know what I mean. I am talking about this:


You shouldn’t evaluate a developer by the number of repositories they have. Some might be “Forked” (Github slang) or they might be their own.

Batch sourcing

Let’s say that you went to a project and found a few hundred members.

You could scrape the list of members and then the profiles.

You could scrape them using Bash or Python…oh yes, this requires some coding skills.

Scraping and Regex

Ideally you are doing a scraping using Python and xpath. So that you can get only the nodes in the DOM that correspond to the data that you want.

If you are using Bash which is not ideal but somehow does the job.

Scraping Contributors

The page loads the content using JS so there is no way to scrape the content from the source code.

Copy Paste the contents of this page into Sublime and use Regex to create a CSV.

Use a Regex Macro in Sublime.

Scraping Members

The source code for this page reflects the same content that is loaded. You could use wget to scrape it or a Python script.

Scraping Profiles

Use a bash script to get source code.

Then use a Regex Macro in Sublime to convert data to a CSV.

Emails from Hex to ASCII

When you scrape these profiles you will see that the emails are encoded in Hex.

Each hex code has a &# followed by an x and 2 digits.

First you need to do a replacement:


Replace with:

Now those emails should look like this:


Reviewing CSV

At this point it should be a good idea to open the CSV file in Excel.

The problem with CSV is that the encoding of characters is different. So for instance, accents or letters like ñ will not show up correctly.

Open the CSV in Sublime and also create a new Excel file.

Remove every column after the first comma, so that you can see only the content of one of the columns displayed. You can use this Regex:


Replace with:

Copy paste that column into excel

Go back to Sublime and UNDO. Now remove the column that you copied with this Regex:


Replace with:

Repeat the process with the rest of the columns.

Decoding the emails

If you do this transformation:

$ echo -e "\x79\x61\x73" | cat

You will be able to transform from hex to ASCII.

$ echo -e supports the following escape sequence:

\xHH the eight-bit character whose value is the hexadecimal value HH (one or two hex digits)

If you add this to a script you will be able to batch convert all the emails into human readable text.

Leave a Reply