View a project on GitHub in action, to see its functionality

You can try and reverse how pull requests happen.

1. Go to your fork

2. Issue a Pull Request

   By default this will be your fork on the right (head repo) requesting to push its commits and changes to the original repo (base repo) on the left.

3. Click the drop down for both base repo and head repo and select each other's repos.

   You want yours listed on the left (accepting changes) while the original repository is on the right (the one with changes to push). As illustrated in this image:

   

4. Send the pull request

   If your fork has not had any changes, you should be able to automatically accept the merge.

If your code somehow conflicts or is not quite clean enough, then this will not work to update via the GitHub web interface and you will need grab the code and resolve any conflicts on your machine before pushing back to your fork.

It's now a baked in feature under the GitHub Traffic section.

You can now see detailed analytics data for repositories that you're an owner of or that you can push to. Just load up the graphs page for your particular repository and you'll see a new link to the traffic page.

The old method used to be some hack like adding an image or similar web bug to your README file.

When someone comes across your repo, provided your README has an extension that GitHub will automatically render, then it should also load the image. And that should, depending on how the web bug is set up, give you some detail or clue as to the source of traffic.

Or you could appeal via contact to the GitHub Supportocats and see if they're willing to give you a heads up on the incoming source of the sauce.