coveralls-public
coveralls-public copied to clipboard
lemurheavy
Public repos missing
It seems that coveralls can't detect all my public repos? I just made an account to add coveralls to the public repo but to no avail. My repository is missing from my public repo list.
For example, coveralls does not list https://github.com/StoneCypher/jssm
This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
@StoneCypher apologies. We're resource-limited and trying to use an automated strategy to prioritize issues by closing older ones. Thanks for replying. I've labeled the issue. Core team will address asap.
@afinetooth - if you're open to a recommendation, i have stalebot set up to add a tag in the time i actually care about, and to close after 999 years
makes it easy to prioritize by just searching on issues with -label:stale
This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.
@StoneCypher thanks for the recommendation. We will look into that. I am personally not so familiar because I did not set it up, but I have submitted a card to our backlog regarding the change.
As for this issue, it's a tough one because it usually has a root cause specific to each user, so without the user's specific details we can't resolve.
Given the issue goes back to 2017, I hope you're not still experiencing the issue, but if you are, please share your username and/or subscription name and I will look into what's behind this for you.
If we can resolve your specific question then we can close this issue as a potential resource for some users.
Otherwise, the ideal situation would be a new issue with relevant, timely user details so we can explain the pattern of the issue as a potential fix for some users.
Yes, I am.
I stopped using coveralls as a result in 2019.
I recently started again because NPM docks your quality rating of you don't put your coverage analysis online.
However, years of staff ignoring that the basics don't work, and setting up robots to throw away knowledge of serious problems that they don't feel like handling?
I switched to an open source hobby project by some guy, because it works, and he responds to bugs
Please stop looking for reasons to close bugs you haven't fixed.
The imperative is to fix bugs, not to keep ticket numbers down
I'm sorry you're still experiencing the issue.
In terms of the details we need to assess the issue for you, it's helpful to know you're on Github because we support other git services, so thanks.
In addition to your git service, though, we'd also need to know if any of the "missing" repos are associated with any orgs you belong to.
Also, if some but not all public repos are accessible to you, we'd need the details on at least one repo that's not accessible, so we can compare the API response we get for it to that for your accessible repos.
For your case, first I see a potential underlying issue, which is a second user account associated with your email but no git service username. That record was created in 2014. I deleted it, since you should not be able to login as such, but I want to ensure we can never grab that user from any lookups by email. (Not aware we would ever do that, just want to eliminate the possibility.)
After that, taking just the public repos available for StoneCypher at Github, when I make a request for available public repos, I get a count of 448, which matches the info here: https://github.com/StoneCypher?tab=repositories
So that indicates that if there's an issue of not seeing some of those repos, it may be that one of our views is not rendering all the ones we're able to see.
When I look at the ADD REPOS page (https://coveralls.io/repos/new) for your user, I see that we still see a count of 448 repos and that you've added 8 of those, so far, to coveralls:
And when I filter the full list of addable repos by StoneCypher, I see 448 repos:
20 repos per page:
23 pages long, with 22 full pages (440) + 8 repos on page 23 = 448 repos:
So that looks right to me. Is that not what you were seeing before?
Is it what you are seeing now?
I notice that you belong to over 25 other orgs, so if the issue relates to one of those, let me know.
I would really rather my repos not be listed in public this way, even the ones that aren't marked private?
This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.
this is not stale. it's just five years ignored on a dead product by a dead staff
i'll keep this open so that people know you aren't safe
hey @nickmerwin , you've got paying customers
could you fix this please?
Hey, I have the same problem, unfortunately.
I just started using coveralls.io.
I can't see any of my repos, neither public nor private, and I can't add anything. It doesn't find any of my repos, see screenshot:
However, I definitely linked my account to coveralls:
… and I even added the Coveralls Github Action to one of my repos and published .lcov files:
https://coveralls.io/github/EricLambrecht/react-timing-hooks
I also added @coveralls as a collaborator to this repo, btw.
Any idea, why it's not working? I could really use some help.
