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
Currently the repository files are stored under ~/.dictconfig/. This is hardcoded and not configurable.
It is ok for interactive usage, but very bad for automation. Thinks of the following scenario:
CI cleans workspace and checks out repository
CI runs dictfile to modify a file in that repository
CI cleans workspace and checks out repository
CI runs dictfile to modify a file in that repository --> this will fail because dictfile will complain that its last committed version is different than the current one, so it will not agree to make changes. The failure is actually good because this feature helps preventing manual modifications to files.
We do however need to support running with a local repository, this way when the CI cleans the workspace, it will also remove the the .dictconfig directory and all will be good.
The text was updated successfully, but these errors were encountered:
Currently the repository files are stored under
~/.dictconfig/
. This is hardcoded and not configurable.It is ok for interactive usage, but very bad for automation. Thinks of the following scenario:
dictfile
to modify a file in that repositorydictfile
to modify a file in that repository --> this will fail becausedictfile
will complain that its last committed version is different than the current one, so it will not agree to make changes. The failure is actually good because this feature helps preventing manual modifications to files.We do however need to support running with a local repository, this way when the CI cleans the workspace, it will also remove the the
.dictconfig
directory and all will be good.The text was updated successfully, but these errors were encountered: