This could be caused by one of three problems.

  1. First and foremost, you need to make sure that you've connected the desired GitHub repository to your corresponding Sifter project. Here's how to setup the GitHub integration.
  2. You may need to link your GitHub profile to your Sifter account. Here's how to link your GitHub account. Once that step is complete, we'll be able to recognize your commits and update your issues.
  3. If you've done steps one and two, the most likely problem is that your local Git configuration isn't setup with one of your recognized email addresses. When you link your GitHub profile to Sifter, Sifter receives all of your email addresses that you've associated with GitHub. When Sifter receives commits, it uses these email addresses to identify you. So if your local Git config email doesn't match one of these recognized email addresses, we won't know who you are. The best solution is to update your Git config to use one of the recognized email addresses. If, however, you need to use an email address that isn't listed under the recognized email addresses, you may need to unlink and re-link your GitHub profile so that Sifter can pick up any new email addresses that you may have added to GitHub.

If all of these solutions don't solve your problem, just send us an email, and we'll get to the bottom of things.