File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -1049,9 +1049,9 @@ the user when it detects an issue:
1049
1049
* When rewriting commit hashes in commit messages, there are a variety
1050
1050
of cases when the hash will not be updated (whenever this happens, a
1051
1051
note is written to `.git/filter-repo/suboptimal-issues`):
1052
- * if a commit hash does not correspond to a commit in the old repo
1053
- * if a commit hash corresponds to a commit that gets pruned
1054
- * if an abbreviated hash is not unique
1052
+ ** if a commit hash does not correspond to a commit in the old repo
1053
+ ** if a commit hash corresponds to a commit that gets pruned
1054
+ ** if an abbreviated hash is not unique
1055
1055
1056
1056
* Pruning of empty commits can cause a merge commit to lose an entire
1057
1057
ancestry line and become a non-merge. If the merge commit had no
You can’t perform that action at this time.
0 commit comments