ThingWorx Git Extension– Changes not reverting after Checkout Commit

[MA8731174]

Hi everyone,

I’m facing a small issue with ThingWorx Git extension.

Let’s say I have exported a project and made a small change in one of the services (but haven’t committed it yet). Then I decide that I don’t want to keep this change and want to revert back to the previous commit version of the project.

Even though I use “Checkout Commit” and then import the entity again, the old version of the service doesn’t appear — the change is still there.

Everything works fine normally when I commit and push, but in this case (uncommitted local changes that I want to discard), it seems not to revert the entity properly.

Right now, my only workaround is to commit the unwanted change with a dummy message, and then go back to the previous commit using Checkout Commit — but that’s not really ideal.

Has anyone found a better way to completely revert to a previous commit and restore entities (like services) to their exact older state without committing the unwanted change first?

Thanks in advance for any suggestions!

[MA8731174]

.

[slangley]

Hi @MA8731174 

To ensure we're on the same page, can you provide the link for the download?

Regards.

--Sharon

[MA8731174]

Hi @slangley  This extension is not supported by ptc but i still posted about it here because so many developers use this extension thats why i have posted it here. 

https://github.com/PTCInc/thingworx-gitbackup-extension

[slangley]

Hi @MA8731174 

It's perfectly fine to post here about any extension--whether PTC supported or not.  I just wanted to confirm the extension you're using so that everyone is on the same page.

I'll reach out to the contributors on this extension to assist with your questions.

Regards.

--Sharon

[VladimirRosu]

Hi @MA8731174 ,

First, thanks for reporting this issue via the GitHub's Issue system - that's the way, I'm working on it.

For others who might read this port, a reminder that all issues encountered when using this extension are required to be reported here:

Below a screenshot of the guidelines to report issues I modified now in the official GitHub page (I realized I wrote about this topic in the past in the announcements I did in the community, but I did not made these guidelines clear in the README.md)

[slangley]

Hi @MA8731174 

If you found the response from Vladimir helpful, please mark it as the Accepted Solution for the benefit of others in the community. 

Regards.

--Sharon

[MA8731174]

Thank you, Sharon.
Vladimir is currently looking into the issue, and once he provides the solution, I’ll update this post and mark it as resolved.

Best regards,

[VladimirRosu]

Hi @MA8731174 ,

I researched and provided information in the Jira Issue about what should be done to change the existing behavior (which seems to be the default checkout behavior).