Skip to content

More explicit mention of --force consequences #731

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.

Sign up for GitHub

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

Open
nh2 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

More explicit mention of --force consequences #731

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions Documentation/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,8 @@ this does not look like a fresh clone.
[...]
Please operate on a fresh clone instead. If you want to proceed
anyway, use --force.
This may delete your reflog, stash, remotes, and other things
you may not expect, so do read the --force docs first!
```
If you then added `--force`, well, you were warned.

Expand Down
4 changes: 3 additions & 1 deletion git-filter-repo
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3414,7 +3414,9 @@ class RepoFilter(object):
"this does not look like a fresh clone.\n"
" (%s)\n%s"
"Please operate on a fresh clone instead. If you want to proceed\n"
"anyway, use --force.") % (reason, msg))
"anyway, use --force.\n"
"This may delete your reflog, stash, remotes, and other things\n"
"you may not expect, so do read the --force docs first!") % (reason, msg))

# Avoid letting people running with weird setups and overwriting GIT_DIR
# elsewhere
Expand Down