-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Open
Labels
Needs: Community DiscussionThis issue is to be brought up in the next community call. [managed]This issue is to be brought up in the next community call. [managed]Needs: LeadNeeds: TriageThis issue needs triage. The team needs to decide who should own it, what to do, by when. [managed]This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed]Type: QuestionThis issue doesn't require code. A question needs an answer. [managed]This issue doesn't require code. A question needs an answer. [managed]
Description
Question
Back until about Sept 11, 2025 there was a bot that commented about our code coverage on each PR (like this).
It seems it stopped working without any PR or issue talking about it. Not sure if we turned it off or it just broke on it's own.
Do we want to:
- Try to enable it again
- Remove the related code (pytest-cov and the github actions configs) ?
Seems like it's probably not that useful to us? Might be better to have AI bot that instead says "hey you should add tests for this" instead of just the coverage bot.
Additional context
Related to this issue I opened recently about the dependency alone.
#11750
Issue resolution criteria
Stakeholders
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Needs: Community DiscussionThis issue is to be brought up in the next community call. [managed]This issue is to be brought up in the next community call. [managed]Needs: LeadNeeds: TriageThis issue needs triage. The team needs to decide who should own it, what to do, by when. [managed]This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed]Type: QuestionThis issue doesn't require code. A question needs an answer. [managed]This issue doesn't require code. A question needs an answer. [managed]