The fetch command has been updated to run asynchronously, allowing for
better performance and responsiveness in the application. This change
ensures that the command does not block the main thread, enhancing the
user experience when interacting with repositories.
Fetch command now uses async/await for non-blocking execution
Added a grace period to prevent immediate background fetch after
switching repositories
Improved handling of authentication errors during fetch operations
The fetch command has been updated to run asynchronously, allowing for
better performance and responsiveness in the application. This change
ensures that the command does not block the main thread, enhancing the
user experience when interacting with repositories.
- Fetch command now uses async/await for non-blocking execution
- Added a grace period to prevent immediate background fetch after
switching repositories
- Improved handling of authentication errors during fetch operations
Christoph
added 1 commit 2026-07-03 15:15:45 +00:00
The fetch command has been updated to run asynchronously, allowing for
better performance and responsiveness in the application. This change
ensures that the command does not block the main thread, enhancing the
user experience when interacting with repositories.
- Fetch command now uses async/await for non-blocking execution
- Added a grace period to prevent immediate background fetch after
switching repositories
- Improved handling of authentication errors during fetch operations
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The fetch command has been updated to run asynchronously, allowing for
better performance and responsiveness in the application. This change
ensures that the command does not block the main thread, enhancing the
user experience when interacting with repositories.
switching repositories