-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Closed
Labels
BugSomething isn't workingSomething isn't workingGit PlatformIssues related to the git & the app platformIssues related to the git & the app platformGit ProductIssues related to version control productIssues related to version control productMediumIssues that frustrate users due to poor UXIssues that frustrate users due to poor UXNeeds TriagingNeeds attention from maintainers to triageNeeds attention from maintainers to triageProductionUX ImprovementVerifiedWhen issue is retested post its fixedWhen issue is retested post its fixed
Description
Is there an existing issue for this?
- I have searched the existing issues
Description
When we pull remote changes into our branch, we do not see a loading state or a response that lets the user know that his action has been performed for at least a few seconds. This will lead the user to click the pull button multiple times till they realise that the changes are being pulled.
Steps To Reproduce
Screen.Recording.2024-02-27.at.8.48.24.AM.mov
- For a git connected app, make changes to the remote branch.
- Now come to the app and refresh the page.
- Click on the pull button in the bottom bar.
Expected: As soon as the user clicks on the pull button, they should get a response/loader which lets them know that the changes are being pulled.
Actual: No visual feedback is given to the user for 6-7 seconds.
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud
Metadata
Metadata
Labels
BugSomething isn't workingSomething isn't workingGit PlatformIssues related to the git & the app platformIssues related to the git & the app platformGit ProductIssues related to version control productIssues related to version control productMediumIssues that frustrate users due to poor UXIssues that frustrate users due to poor UXNeeds TriagingNeeds attention from maintainers to triageNeeds attention from maintainers to triageProductionUX ImprovementVerifiedWhen issue is retested post its fixedWhen issue is retested post its fixed