-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document necessary config changes #2040
Comments
@sqrt Sorry but I am unaware of what config changes you are referring to. We have not in any recent changes required any user changes to update. There should be no need for a user to manually migrate configuration assuming you follow some simple rules:
Any time we have changed a config file name/location/format/content we have written in automation to handle that change for the user. Cmder should see that changes are required and do all required changes for you on first run after upgrading. If this is not the case can you please provide a detailed example of where this did not work for you. |
README.md updated #2041 |
@sqrt was the above helpful? |
Closing due to lack of response from OP. |
I find it very hard to keep track of what changed between releases, and what I need to do to migrate my configuration. It regularly happens that some config location changes, or the name of options, or something like that, and we have to find the respective PR to see what actually changed.
The release notes/Changelog is not exactly helping, case in point for 1.3.7:
How am I supposed to understand what is necessary from user perspective to migrate configuration? Am I supposed to check all PRs and see what exactly has changed?
It would be great to get a "Changes Required" chapter in the release notes, with easy-to-grasp required actions such as "Rename you
user-aliases
file touser_aliases
", "Move yourconemu.xml
to the vendor folder", "Add the following line toProfile.ps1
" or whatever.The text was updated successfully, but these errors were encountered: