Uncommitted Changes

[edonle]

I'm using coArchi 0.87 and have just updated Archi to version 5.02 on Windows. After updating to the new version I'm getting messages that there are changes to commit (in any branch) without me having made any changes to the models. The same happens when I abort uncommitted changes. Can anyone help or have any idea what's going on?

[Phil Beauvoir]

Hi, this is probably the Archi model version number. When a new version of Archi is released with major changes, the internal Archi model number is increased. You won't see it, but it's safe to commit anyway.

[johmut]

Hi Phil,

I have the same issue as the OP. In fact, I can commit or abort local changes all I want, the message "There are changes to commit" does not go away. The issue appeared after a combined upgrade to Archi 5.0.2 and coArchi 0.8.8
Refresh and Publish works as expected, the reposiory remains 'red' in the Collaboration Workspace

Thx & KR,
johmut

[Phil Beauvoir]

Hi, hard to say without actually having access. The "red" status might be bogus. Perhaps anther git tool might show if there is actually something to commit?

[johmut]

Hi Phil,
Things are getting worse for me ...
My repository is 'red' in the Collaboration Workspace as there are 'uncommitted changes'? (posted above)

When I richt-click on the repository in the Collaboration Workspace and select Refresh, it completes without error. When I right-click an element in the model tree and select Collaboration > Refresh Model, it asks for a commit message, my master password (to the credentials stored in the encrypted file) and then fails with a remote repository path/repository name.git not Authorized error. I can use the gitlab webUI on the remote server using the same UID/PWD without any problems. It all started after my upgrade to Archi 5.0.2 and coArchi 0.8.8. Any clue?
Anything I can check client-side in .log files? As I don't have access to server side CLI and .log files.

KR,
Johmut

[johmut]

OK, I figured it out. Here's what was needed...

For some reason the remote-repository in the Collaboration Workspace referred to a local repository in the new location Documents\Archi\model-repository, while the Model Tree Explorer had the local repository open from its old location in AppData\Roaming\Archi\model-repository. I was happily architecting in the local repository, yet suffered the .......git Not Authorized error when I tried to refresh or publish from the Model Tree Explorer. Understandably so, with hindsight 20/20.

I had to use all the tricks in my hat to copy my local repository from the old to the new location, then use Visual Studio' Git Extension to commit, stage, pull and push from local to the remote repository (which worked), then remove and recreate an empty model-repository folder in the new location, fire up Archi, Import the remote workspace to have it rebuild a local .archimate file and voilà It Works! A small headache is all what remains.

Hope this is useful to help other people.

KR,
Johan