Skip to content

fix(issues): group bot issues#260

Merged
ReenigneArcher merged 1 commit into
masterfrom
fix/issues/group-bot-issues
May 23, 2026
Merged

fix(issues): group bot issues#260
ReenigneArcher merged 1 commit into
masterfrom
fix/issues/group-bot-issues

Conversation

@ReenigneArcher
Copy link
Copy Markdown
Member

Description

Collect open issues (excluding PRs), detect bot-authored issues, and surface counts in build output and the dashboard.

  • src/updater.py: add _collect_open_issues and helper to detect PRs, persist per-repo issues JSON.
  • src/helpers.py: add is_bot_issue_author and a list of known bot logins.
  • src/builder.py: read cached issues, compute total, bot and other issue counts, and include issues_bot/issues_other in repo entries.
  • gh-pages-template/assets/js/dashboard.js: add issueCounts and renderIssuesBarChart to show stacked Bot vs Other issues (log-scaled) and wire it into dashboard load/export.
  • Tests: update/add unit and integration tests to cover issue reading, bot classification, updater behavior, and dashboard rendering.

This enables distinguishing bot-opened issues from others and displays them in a dedicated stacked issues chart.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

@codecov
Copy link
Copy Markdown

codecov Bot commented May 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (42ba71e) to head (4286631).
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##            master      #260   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          955      1017   +62     
=========================================
+ Hits           955      1017   +62     
Flag Coverage Δ
Linux 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
gh-pages-template/assets/js/dashboard.js 100.00% <100.00%> (ø)
src/builder.py 100.00% <100.00%> (ø)
src/helpers.py 100.00% <100.00%> (ø)
src/updater.py 100.00% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42ba71e...4286631. Read the comment docs.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ReenigneArcher ReenigneArcher force-pushed the fix/issues/group-bot-issues branch from d953817 to 4a501fe Compare May 23, 2026 03:12
Collect open issues (excluding PRs), detect bot-authored issues, and surface counts in build output and the dashboard.

- src/updater.py: add _collect_open_issues and helper to detect PRs, persist per-repo issues JSON.
- src/helpers.py: add is_bot_issue_author and a list of known bot logins.
- src/builder.py: read cached issues, compute total, bot and other issue counts, and include issues_bot/issues_other in repo entries.
- gh-pages-template/assets/js/dashboard.js: add issueCounts and renderIssuesBarChart to show stacked Bot vs Other issues (log-scaled) and wire it into dashboard load/export.
- Tests: update/add unit and integration tests to cover issue reading, bot classification, updater behavior, and dashboard rendering.

This enables distinguishing bot-opened issues from others and displays them in a dedicated stacked issues chart.
@ReenigneArcher ReenigneArcher force-pushed the fix/issues/group-bot-issues branch from 4a501fe to 4286631 Compare May 23, 2026 03:20
@sonarqubecloud
Copy link
Copy Markdown

@ReenigneArcher ReenigneArcher merged commit 5c5b3a4 into master May 23, 2026
17 checks passed
@ReenigneArcher ReenigneArcher deleted the fix/issues/group-bot-issues branch May 23, 2026 03:29
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.

1 participant