Closed roberthoenig closed 6 years ago
@zulipbot claim
Welcome to Zulip, @swekshajha12! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
Hello @swekshajha12, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 10 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!
Update: All the original bots mentioned in this issue have either been deleted, deprecated, or given tests.
The next step here is to move the remaining bots in zulip_bots/bots
to 100% test coverage. Currently, none of them is at 100%. Their coverage ranges from 50% - 95%, the mean is ~80%. Details can be found in the codecov coverage report.
@zulipbot claim
Welcome to Zulip, @palash25! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
@roberthoenig can i take up this issue?
@starlord1311 no I'm working on it if I can't complete it in the next 5 days I will be unassigned and then you can try
@zulipbot Claim
@zulipbot claim
Hello @ViRu-ThE-ViRuS, 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!
@roberthoenig is this Issue still under Progress?
@salman-bhai this issue can be worked on by multiple people - claims with zulipbot do technically not make a lot of sense. Feel free to just choose a bot and improve its test coverage :)
Welcome to Zulip, @AmAnAgr! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
Alright @roberthoenig thanks a lot !
@zulipbot claim
re-opening
@zulipbot claim
@zulipbot abandon
ERROR: This active issue has no assignee.
ERROR: This active issue has no assignee.
Here is a list of remaining bot files not at 100% coverage:
Do the ones at 97%-plus coverage have some common thing missing?
Most of them require raising Exceptions after requests.get/post method.
@zulipbot claim
Welcome to Zulip, @DhruvThakker! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
claim
@zulipbot claim
Welcome to Zulip, @kishanlp! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
UPDATE Scroll down to the latest comments to find a list of the remaining bot files not at 100% coverage.
NOTE: All striked-through bots have been deprecated, all checked bots have been given tests. See the comments for more information on how to proceed.
We have a couple bots in
zulip_bots/zulip_bots/bots
that are untested:- [ ] commute- [ ] foursquare- [ ] git_hub_comment- [ ] github- [ ] googlesearch- [ ] howdoi- [ ] john- [ ] youtubeFor each bot, we should either
add tests. You can find help in our guide for bot testing.
deprecate the bot. If a bot seems to be bugged or completely useless, we should discuss it on chat.zulip.org and decide whether it is worth keeping.