where <message> is "Manual Commit" for the first case and "Checkpoint" for the second
but from there in the second case, I could see creating a tag with the current date[time] and "Checkpoint" as the message... or I could see squashing all the commits since the last "tagged" commit and then rewording the combined commit with the tag message.
That second version mirrors my current workflow, but I'm not sure how aggressively I want to push that since it's so hard to undo.
GIVEN Alex already has
gsb
installed on her system and is using it to track a save stateWHEN she opens a terminal, navigates to the directory where her save game lives and runs the command:
THEN
gsb
will create an incremental backup of the registered save file (see #1), including any new files added or removed to parent directoriesAND ALSO
WHEN she runs the command:
THEN
gsb
will create the incremental backup in a way that annotates the backup the message "Checkpoint"SO that she doesn't have to run the
git
commands herselfNotes
Under the hood, this is:
where
<message>
is "Manual Commit" for the first case and "Checkpoint" for the secondbut from there in the second case, I could see creating a tag with the current date[time] and "Checkpoint" as the message... or I could see squashing all the commits since the last "tagged" commit and then rewording the combined commit with the tag message.
That second version mirrors my current workflow, but I'm not sure how aggressively I want to push that since it's so hard to undo.