-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find a way to set the GitHub username #255
Comments
There is a similar problem for issues on GitLab repos, which ideally should mention a GitLab username instead of a GitHub username. The GitLab issue also appears for the web-frontend with https://gitlab.com/coala/landing/issues/31 Ultimately, we need a database. IMO, we should use a gspread or bitrix24 as the datastore. |
And we also have this problem with Zulip, which is based on email addresses. One approach is to have a 'github username' method, which each backend service implements to convert what it has, to a github username. For the Zulip backend, it is easy to do an email address lookup via the GitHub API. |
@jayvdb Personally, using spreadsheet services is more of a hack rather than an actual solution for databases. Since this is essentially a key-value situation, something like Redis (or an even more permanent) solution would be preferable rather than a fully blown spreadsheet application for such athing. |
Most services will at least tell you what their email is. If corobo fails or the service simply doesn't have that luxury, we can just simply ask the person to set it manually. For example:
|
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 ixes coala#392 elated to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 ixes coala#392 elated to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 ixes coala#392 elated to coala#255
Some backends do not provide usernames or msg links. Zulip and Slack both using msg.extra['url'], and a patch is pending for the gitter backend to follow suite. errbotio/err-backend-gitter#32 Fixes coala#392 Related to coala#255
Maybe we also add some |
LabHub assumes the username is always a GitHub username, while this works for gitter. It doesn't work for other platforms such as Telegram, IRC, etc
Opened by @yukiisbored at gitter//yukiisbored
The text was updated successfully, but these errors were encountered: