You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add PR conflict detection using GitHub API mergeable field
- Fetch mergeable field from GitHub API in GitService
- Add has_conflicts getter to PRStatus model
- Display warning emoji (⚠️) for PRs with conflicts
- Prioritize conflicts in highlighting system
* Fix PR conflict detection to use string values from GitHub API
- Changed mergeable type from boolean to string (MERGEABLE/CONFLICTING/UNKNOWN)
- Updated has_conflicts getter to check for 'CONFLICTING' string value
- Fixed is_ready_to_merge to require mergeable === 'MERGEABLE'
- Added comments documenting the possible enum values
* Rework PR conflict detection using local git operations
- Added async checkMergeConflictsAsync() method to GitService
- Uses local git test merge to detect conflicts (no GitHub API needed)
- Added has_merge_conflicts field to GitStatus model
- Created async getGitStatusAsync() method with parallel operations
- Display conflicts in CHANGES column with warning emoji (⚠️)
- Added async git status refresh every 5 seconds
- Conflicts given high priority (Priority 2) in highlighting
- Removed mergeable field from PRStatus (was using GitHub API)
Benefits:
- Works without network/GitHub API access
- Faster local detection
- Shows conflicts even for branches without PRs
- Non-blocking async updates
- Conflicts shown in actionable CHANGES column
* Revert to GitHub API-based conflict detection
- Restored mergeable field to PRStatus model (MERGEABLE/CONFLICTING/UNKNOWN)
- Added back mergeable field fetching in GitService PR methods
- Display conflicts in PR column with ⚠️ emoji (not CHANGES column)
- Restored PR-based highlighting priorities for conflicts
- Removed async git status methods and local conflict detection
- Removed unused useGitStatusAsync hook
- Conflicts now shown in PR column as originally implemented
This reverts back to using GitHub's built-in mergeable API field
for conflict detection instead of local git operations.
0 commit comments