The low-level history.get_history method now has the option to force the inclusion of the most recent commit, regardless of whether it's tagged or if it was created by GSB
gsb history uses this flag to always return the most recent "backup" at the top of the list
The gsb rewind prompt will now show the most recent commit as "Option 0."
Tests have been refactored (and rewritten) so that the session "_repo_with_history` fixture now includes a post-tag commit and a post-commit change
The CLI messages have been tweaked slightly (with a nod towards #44)
Tech Debt and Other Concerns
The "zeroth" rewind option may be a duplicate of the first, but I have zero problem with that.
Validation Performed
Ran gsb history and gsb rewind on this project's Git repo with the expected outcome. Also tried them out on a GSB-managed repo.
[x] I have run mkdocs serve locally and ensured that all API docs and
changes I have made to the static pages are rendering correctly, with all links
working
[x] All tech debt concerns have been resolved, documented as issues, or otherwise
accepted
Summary
Resolves #30
List of Changes
history.get_historymethod now has the option to force the inclusion of the most recent commit, regardless of whether it's tagged or if it was created by GSBgsb historyuses this flag to always return the most recent "backup" at the top of the listgsb rewindprompt will now show the most recent commit as "Option 0."Tech Debt and Other Concerns
The "zeroth" rewind option may be a duplicate of the first, but I have zero problem with that.
Validation Performed
Ran
gsb historyandgsb rewindon this project's Git repo with the expected outcome. Also tried them out on a GSB-managed repo.PR Type
release)Checklist:
mkdocs servelocally and ensured that all API docs and changes I have made to the static pages are rendering correctly, with all links working