Skip to content
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

Show outgoing webhook bot token in bot settings. #12943

Open
jdherg opened this issue Aug 6, 2019 · 9 comments · May be fixed by #13556
Open

Show outgoing webhook bot token in bot settings. #12943

jdherg opened this issue Aug 6, 2019 · 9 comments · May be fixed by #13556

Comments

@jdherg
Copy link
Contributor

jdherg commented Aug 6, 2019

The "Your Bots" page bot cards should show the token for outgoing webhook bots along with the username, API key, etc. As far as I can tell, the only way for a bot developer to get the token now is to pull it out of the Zulip Botserver config that can be downloaded from that page.

@zulipbot
Copy link
Member

zulipbot commented Aug 7, 2019

Hello @zulip/server-settings members, this issue was labeled with the "area: settings (user)" label, so you may want to check it out!

@timabbott
Copy link
Sponsor Member

Agreed.

@sahil839
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Oct 29, 2019

Hello @sahil839, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@sahil839
Copy link
Collaborator

@zulipbot claim

sahil839 added a commit to sahil839/zulip that referenced this issue Dec 19, 2019
Bot token is displayed for outgoing webhook bots in the "Your Bots"
section of settings and position of displaying bot type is changed
to top right.

Fixes zulip#12943
@sahil839 sahil839 linked a pull request Dec 19, 2019 that will close this issue
@zulipbot
Copy link
Member

zulipbot commented Dec 29, 2019

Hello @sahil839, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@wryonik
Copy link
Collaborator

wryonik commented Feb 17, 2020

@timabbott @sahil839 is this issue still available? I see a PR related to it but it has no activity for a long time

@sahil839
Copy link
Collaborator

@shubhamgupta2956 I think you should find an other issue to work on as the PR is completed and hopefully will be merged soon.

@wryonik
Copy link
Collaborator

wryonik commented Feb 18, 2020

Ok, thanks :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants