Skip to content

Conversation

@prosdev
Copy link
Collaborator

@prosdev prosdev commented Dec 14, 2025

Summary

This PR includes three main improvements:

  1. Bug Fix: Fixed dev owners showing "No ownership data" when run from subdirectories
  2. Visual Improvements: Added tree branches and file icons to dev map and dev activity outputs
  3. GitHub Stats Fix: Fixed confusing issue/PR state display (was showing wrong open PR count)

Changes

Bug Fixes 🐛

  • dev owners: Fixed path matching to correctly display ownership data when run from subdirectories
  • Progress Display: Fixed NaN showing during initial file discovery phase
  • dev update: Removed duplicate checkmark in success message

Visual Enhancements ✨

  • Added tree branches (├─, └─) and file icons (📘, 📝, 🐹, etc.) to dev map hot paths
  • Added tree branches and file icons with vertical connectors to dev activity output
  • Extracted getFileIcon() to shared utility in @lytics/dev-agent-core

GitHub Stats Fix 🐛

  • Fixed confusing display showing "14 open PRs" when there were actually 0
  • Added separate state tracking: issuesByState, prsByState
  • GitHub indexer now tracks issue and PR states independently
  • Stats display now shows accurate per-type counts

Progress Display Improvements 📊

  • All indexing commands show detailed progress: 1,234/4,567 files (27%, 45 files/sec)
  • dev update now shows an update plan before starting
  • Refactored progress logic into ProgressRenderer.updateSectionWithRate()
  • Applied detailed progress to: dev index, dev update, dev git index, dev github index

Testing

  • ✅ All tests passing (including updated map test)
  • ✅ Tested dev owners from root and subdirectories
  • ✅ Tested dev stats with updated GitHub state tracking
  • ✅ Tested dev activity, dev map with new visual formatting
  • ✅ Tested progress display across all indexing commands

Breaking Changes

None - all changes are backward compatible. Old GitHub state files fall back to aggregate counts gracefully.

Fixed 'No ownership data found' error when running dev owners
from subdirectories like packages/.

Root cause: File paths in topFiles are absolute (from database),
but subdirectory mode was comparing them against relative paths.

Solution: Normalize absolute paths by stripping repository prefix
before comparison, matching the approach used in root directory mode.
- Add update plan display to 'dev update' (shows what will change before starting)
- Add detailed progress with rates to all indexing phases (files/sec, docs/sec, commits/sec)
- Extract progress formatting to reusable updateSectionWithRate() method
- Fix NaN display when totalFiles is 0 (now shows 'Discovering...')
- Improve 'dev map' hot paths display with tree branches and file icons
- Add getUpdatePlan() public method to RepositoryIndexer

All indexing commands now show consistent detailed progress:
  1,234/4,567 files (27%, 45 files/sec)

Instead of just:
  27% complete
Visual Improvements:
- Add tree branches and file icons to 'dev map' hot paths
- Add tree branches and file icons to 'dev activity' output
- Extract getFileIcon() to shared utility in @lytics/dev-agent-core

GitHub Stats Fix:
- Track issue and PR states separately (issuesByState, prsByState)
- Fix confusing display showing '14 open PRs' when there were 0
- Add proper per-type state counts to GitHubIndexStats interface
- Update display to show accurate counts for issues and PRs

Progress Display Enhancements:
- Add detailed scanning progress with rates (e.g., '1,234/4,567 files (27%, 45 files/sec)')
- Extend detailed progress to 'dev update', 'dev git index', and 'dev github index'
- Add update plan display to 'dev update' (shows changed/added/deleted before starting)
- Refactor progress formatting into reusable updateSectionWithRate() method
- Fix NaN display when totalFiles is 0 (now shows 'Discovering files...')

Test Updates:
- Update map test to match new hot paths format with tree branches

All visual outputs now use consistent tree-based formatting with file icons.
@prosdev prosdev merged commit 5c2b101 into main Dec 14, 2025
1 check passed
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