You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 3 main actions in the collaboration menu are :
Refresh Model
Commit Changes
Publish Changes
Maybe it is because I also know git, but I was always wondering if the "Publish changes" was also "refreshing model", so I used to do both "Refresh" then "Publish".
Yes, I also noticed that most users don't get the exact actions behind Refresh and Publish. In the same vein, I've seen lots of people running Commit and then Publish: in this context Commit is not needed because it will be triggered anyway by Publish, so this ends up taking twice the time (which can mean a lot of time if model is big and some anti virus is running in the background, slowing down operations).
I don't think we'll change this on current version of coArchi, but that's something we should look at for coArchi2. If possible, I think we should only have a Commit & Sync option (which would act as the current Publish action).
Version of Archi, Operating System
4.9.3 @ Windows
Version of this plug-in
0.8.3
Any other plug-ins installed?
Scripting
Feature request
The 3 main actions in the collaboration menu are :
Maybe it is because I also know git, but I was always wondering if the "Publish changes" was also "refreshing model", so I used to do both "Refresh" then "Publish".
After reading the wiki at https://github.com/archimatetool/archi-modelrepository-plugin/wiki/Refresh-and-Publish I understand that "Publish changes" already does a "refresh" (git pull) prior to pushing, although git commands are not mentionned in the description for "Refresh Model".
It may be clearer to rename the "Publish Changes" action into "Refresh and publish changes"...
The text was updated successfully, but these errors were encountered: