Open
Conversation
philrz
commented
Mar 18, 2026
| Name: "vacate", | ||
| Usage: "vacate [options] [timestamp]", | ||
| Short: "compact a pool's commit history by removing old commit objects", | ||
| Short: "truncate a pool's commit history by removing old commit objects", |
Contributor
Author
There was a problem hiding this comment.
Proposing truncate since compact is already a verb attached to other functionality, and also we're deleting not squashing as the command was once envisioned.
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's Changing
This updates the
db vacatebook docs to match what was added in #6706.Why
The docs being replaced here pre-dated #6706 and were not an accurate representation of what was added.
Details
I'd have liked to include something about when certain
vacateattempts will be rejected such as shown in the bottom test in vacate.yaml. I'm told it has something to do with "common ancestors", but I'm struggling with the wording. If someone can propose the right text I'm game. Otherwise happy to leave for later.While running tests to write this, I spotted #6746.