Skip to content

[usability] ProcessIssues.parse_issues(issues) should have a print /…count indicator so we know it's doing something #191 #261

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

Closed

Conversation

hariprakash619
Copy link
Contributor

Added progress/count indicator in the def parse_issues() method.

Copy link

codecov bot commented Feb 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.34%. Comparing base (4a97ae0) to head (f485b66).
Report is 31 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #261      +/-   ##
==========================================
+ Coverage   76.27%   76.34%   +0.06%     
==========================================
  Files          10       10              
  Lines         725      727       +2     
  Branches       92       92              
==========================================
+ Hits          553      555       +2     
  Misses        162      162              
  Partials       10       10              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@hariprakash619
Copy link
Contributor Author

pre-commit.ci autofix

@lwasser
Copy link
Member

lwasser commented Apr 29, 2025

Hi there! i am going to close this given we made a move to logging in #270 many thanks for your time in opening it!

@lwasser lwasser closed this Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants