Closed EricZimmerman closed 1 year ago
updated a few things from user feedback and some formatting
I think it would be good to add a warning (or even a note) about the potential maintenance issues that auto-generated commit messages might bring.
I am certainly happy to adjust and add such a note but what are your specific concerns as it relates to the auto commit message, that it might create a bunch of different versions of a configuration which may be more difficult to find a specific change?
I am certainly happy to adjust and add such a note but what are your specific concerns as it relates to the auto commit message, that it might create a bunch of different versions of a configuration which may be more difficult to find a specific change?
Exactly. The only difference between the commit messages is going to be the date. So, unless users can remember when they committed a certain change (something that is much more difficult if you are looking for something that happened a year ago), the git log is going to be useless. Users are forced to look at the actual diffs one-by-one.
I realize that this can't be fixed with automatic commits, which is why it worth warning the users of what they are getting into with auto-commits.
Okay. That's not a problem. I'll have this note added within the next 30 minutes or so. Thank you for the review
changes implemented, new note added
Slicer and Print Start work should be more or less done now, pending any feedback
@shiftingtech any chance for a review/merge on either of these?
This PR was initially written for the old path locations, but then updated to support the new moonraker path locations, which should fall back to the old directories once the symlinks are created by moonraker scripts.
Contains screenshots throughout, the ability to copy command lines, and rampant nano usage.
I hope the community finds it useful.