requires configuration of a GitHub Access Token as follows;
GitHub Access Token
In order for the linkback feature to work and the badges to be granted to your users, you need to provide a Github access token. You can generate your token here: https://github.com/settings/tokens/new .
The linkback feature requires the public_repo scope, and granting badges requires no scope (leave everything unchecked if you only want badges). Since the public_repo scope grants write access to repositories, we recommend you create a throwaway Github account that has access to no repositories and use it just to generate a token.
Add one or more URLs of the GitHub repos to scan for contributions to the github badges repos site setting.
For the link backs
Finally, add the projects you wish to post to in the github linkback projects site setting in the formats:
.username/repository for specific repositories
. username/* for all repositories of a certain user
Details: I think there are two fairly separate pieces of functionality here. I think the linkback one is the simpler one, and perhaps you've already observed it. If you mention a github issue in a discussion on discourse, like this:
Then the discourse bot adds a public comment to that issue that links back to this discussion. This should currently be enabled for all of the racket/* repos at github.
The 'badge' piece seems to be almost entirely separate; I believe the github plugin is actually a rewritten combination of two older plugins. For this plugin it appears that we have to add each repo of interest one at a time, no wildcards. (And at this point, I've only added the one repo, racket/racket.) However, you ask a really good question about badge linkage; I have to assume that it's done by email address; that is, the email address associated with the commit has to be the same one associated with the discourse account. I realize that many people (such as myself!) use many different email addresses, and my guess is that in this case, the badges won't work.
I think linkbacks could wind up being useful. The badges... well, we'll see.
Added a bunch more repos for badge consideration, in order of most-recently-updated. There's no really fair way to do this that doesn't involve adding dozens and dozens of repos.
