6

I've contributed to Go, but when I tried to add Go to the "Open Source" section of my Careers profile, Careers refused with the message "Hidden We couldn't find any commits you've made to this project." Why won't Careers display my contributions to Go?

  • Do you have a GitHub account, and is the email address (which is clearly yours) listed as the commit author at api.github.com/repos/golang/go/commits/… associated with your GitHub account? For some reason, GitHub doesn't seem to have linked the commit to any GitHub user. Perhaps you need to associate the email address that you used to make that commit with your GitHub account, or perhaps this is a GitHub bug? Good luck if it's the latter, since they don't have a public issue tracker - you can always email support, I guess. :( – Mark Amery Jan 19 '15 at 8:42
  • @Mark is correct - if GitHub links that commit to your user profile, it will appear as one of your commits in the API, so we'll be able to see it's really you. – Alex Warren Jan 19 '15 at 9:36
4

Edit

The issue originates from Github not linking your commit with your Github account, even though the email addresses (in the commit and on your profile) seem to match.

The issue isn't due to the fact you are an author and not a committer: we actually handle this case.

This looks like an edge case, I manually updated the project status on your profile so that it is not hidden anymore.

Original answer

While you are the author of this commit, you are not the committer. The difference between author and committer is that the author is the creator of the content, while the committer is, well, the committer.

git author vs committer

We unfortunately don't have a way of verifying the relationship between your Github profile and the Go project from the Github API: neither the list of your repos nor the list of contributors to the Go projects provide us with this information.

Your Github profile shows that you are a collaborator to the Go project, but this information is not based on your commits/authoring, but rather on the Issues you've opened on the project.

In this case, it would help if Github included the authors in the list of collaborators, but it's not the case and we haven't found a good way to work around it yet.

  • Unclear what has been done i.e. why is this tagged status-completed? – Shadow The Princess Wizard Jan 18 '15 at 21:51
  • 1
    I marked it as status-bydesign which looks more relevant here, thanks! – Aurélien Gasser Jan 18 '15 at 21:54
  • Thanks! The older report you linked to got official answer from Matt ending with "we'll announce if/when we figure it out" - I failed to see such announcement, can you please update the answer or prod Matt with a sharp stick to do that? ;-) – Shadow The Princess Wizard Jan 18 '15 at 21:57
  • 1
    The linked question was related to another (but similar) problem, I removed the reference to it. This other problem/question has been resolved and the answer updated. – Aurélien Gasser Jan 18 '15 at 22:07
  • I don't think it's true, in general, that you can't verify commit authorship through the API. It's perfectly possible with the GitHub API to query by author instead of by committer. For instance, api.github.com/repos/jquery/api.jquery.com/… lists my (ExplodingCabbage's) contribution to the jQuery API docs, even though kswedburg is the committer. The issue seems to be that the author here hasn't been associated with a GitHub account for some reason: api.github.com/repos/golang/go/commits/… – Mark Amery Jan 19 '15 at 8:37
  • @MarkAmery We indeed use the API route you mention (I had missed it) and the origin of the problem is what you described. Answer updated. Thanks! – Aurélien Gasser Jan 19 '15 at 15:39

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .