#Unable to discard changes

1 messages · Page 1 of 1 (latest)

tiny socket
#

Hi, im trying to discard the changes in order to take a pull from the repo, but it keeps showing this error.

image.png
tribal sedgeBOT
#

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Pranav

tribal sedgeBOT
#

Hey there,

To help us debug the issue, please consider the following steps and provide us
with the information:

  • Try discarding the changes and pulling the changes from the remote branch.
    If discarding changes doesn't work and you still see them, it's probably system
    changes due to the Appsmith version upgrade.
  • By creating and committing to a new branch, you can verify that the
    functionality is intact.
    If everything seems fine, you can merge the new branch into your main branch.
  • If that doesn't work for you, please make a loom recording of the entire
    process and share with us so we can have the full context of the issue.
  • Lastly, let us know the Appsmith version and share server logs
    guide.

Best regards,
Jimmy H

tiny socket
#
  • the same issue persists when we try to discard and pull from the remote branch.
  • we were merging some changes from one branch to the other, and then took a pull from the remote. After taking a pull, we are seeing 30 uncommitted changes in appsmith. (this number 30 also keeps on increasing everytime we try this process)
image.png
#

The version we are currently using is 1.9.15

#

as you can notice, we started with 30 uncommited changes, but then later we see 31 uncommited changes

tiny socket
#

i also tried to create a new application, but getting the same error

image.png
tribal sedgeBOT
tiny socket
#

but the older version was working fine for me until yesterday, why are we seeing this issue out of a sudden from today?

midnight jacinth
#

Hello @tiny socket ,

#

I'm not very certain as to why this might have occurred. However, I have quite a feeling that updating to the latest version might fix this issue for you. A lot of our users have reported several git issues similar to this, which our engineers have taken up and fixed.

Could you try updating to the latest version and give me feedback?

tiny socket