-
Notifications
You must be signed in to change notification settings - Fork 220
/
GitHelp.txt
51 lines (39 loc) · 1.54 KB
/
GitHelp.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
-------------
CLEAR HISTORY
-------------
If you need to remove files from the git history
(to get back space for exemple) you can do it with
git-filter-repo:
* Clone https://github.com/newren/git-filter-repo.git
* Download Python Windows embeddable package (64-bit) from https://www.python.org/downloads/windows/
* Clone https://github.com/MagicFoundation/Alcinoe.git somewhere (!that important to stay safe!)
* Launch a command prompt in the Cloned Alcinoe root directory
* set PATH=C:\Dev\git-filter-repo;%PATH%
* set PATH=c:\Program Files\Python;%PATH%
* git filter-repo --path-glob "Demos/*.exe" --invert-paths --force
* git filter-repo --path-glob "Demos/*.apk" --invert-paths --force
* git remote add origin https://github.com/MagicFoundation/Alcinoe.git
* git push --force --all origin
You can also analyze the list of directories/files that
can be deleted with this command:
git filter-repo --analyze
-----------------------
MAKE GIT CASE SENSITIVE
-----------------------
git config core.ignorecase false
-----------------------
REMAME FILE (case only)
-----------------------
git mv xxx xxx2
git mv xxx2 XXX
-------
Git LFS
-------
To associate a file type in your repository with Git LFS
git lfs track "*.psd"
-----------------------------------------------
fatal: detected dubious ownership in repository
-----------------------------------------------
https://medium.com/@thecodinganalyst/git-detect-dubious-ownership-in-repository-e7f33037a8f
In my case the owner was built-in Administrators group and
my solution was just to change it to me