Closed timabbott closed 2 years ago
@zulipbot claim
Hello @Ponni-M!
Thanks for your interest in Zulip! You have attempted to claim an issue without the labels "help wanted", "good first issue". Since you're a new contributor, you can only claim and submit pull requests for issues with the help wanted or good first issue labels.
If this is your first time here, we recommend reading our guide for new contributors before getting started.
@zulipbot add "good first issue"
@zulipbot claim
Welcome to Zulip, @Ponni-M! 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)!
@timabbott I have added the gist action to my fork, we may need to add the gist access token to this project. You can also refer in my branch if the changes are fixing the issue https://github.com/Ponni-M/python-zulip-api/tree/Ponni-M-patch-1
@zulipbot claim
Welcome to Zulip, @harshakhmk! 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)!
I think the badge is correctly configured in README but it is somehow related to this correct me if I am wrong
Hello @harshakhmk, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days.
If you've decided to work on something else, simply comment @zulipbot abandon
so that someone else can claim it and continue from where you left off.
Thank you for your valuable contributions to Zulip!
https://app.codecov.io/gh/zulip/python-zulip-api seems to not be 0,
But it has no data since 2020-12-02. The GitHub Actions output indicates that it only finds one “coverage report” at ./zulip-api-py3-venv/bin/coverage-3.9
, which is not a coverage report.
@zulipbot claim
Welcome to Zulip, @gvarun1! 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)!
@zulipbot abandon
I checked the badge with both codecov's and shield's images. It seems like only the master
branch is affected for now, but the badges say "unknown" intermittently.
Examples:
master
- irc
with a PR open - codecov
with an open PR - I don't think it's a badge config issue either. It looks like the coverage report is missing from the Github action altogether. In other branches, a ./coverage.xml
seems to be generated, but in master
branch, it wasn't.
One more difference is this line in the output:
In master
:
Python coveragepy not found
In codecov
:
Python coveragepy exists disable via -X coveragepy
-> Running coverage xml
I'll pull the repo in the near future and try to see if I can find anything else.
@zulipbot claim
Welcome to Zulip, @pradeepcep! 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)!
@zulipbot claim
Second time's the charm. Here we go!
@timabbott Looks like the issue isn't there anymore -
I fixed this in #699.
This is likely a side effect of the CircleCI => GitHub migration.
https://app.codecov.io/gh/zulip/python-zulip-api seems to not be 0, so I'm guessing we just have the badge misconfigured.