[Bug]: Post pulling changes, a blank commit still shows up forcing user to commit. #41521
Description
Is there an existing issue for this?
- I have searched the existing issues
Description
After making changes in remote, and pulling it locally, I still see a blank commit show up in the commit dialog of my application, forcing user to commit the change which has been pulled.
Steps To Reproduce
- Post making changes in remote, pull the changes locally on the branch.
- Pull goes through successfully
- Click on the commit dialog, I still see a blank commit show up in the commit dialog
The issue recording is explained in the combination of two videos below:
Video1: https://jam.dev/c/7ec113b9-46d2-47e7-a95a-3402a2f6807b
Continuation - Video2: https://jam.dev/c/6036f7f2-5d82-408c-8c0b-da8ea5ec437a
Note: This issue is not observed on prod [app.appsmith.com]
Public Sample App
No response
Environment
Release
Severity
High (Blocker to building or releasing)
Issue video log
No response
Version
Cloud
Metadata
Metadata
Assignees
Labels
Something isn't workingIssues related to version control productIssues related to information shown on git status modal or number of changes appearing in a branchAn issue that is neither critical nor breaks a user flowNeeds attention from maintainers to triageAll issues belonging to Packages and Git