Branching out with a previous commit in a GitHub project

Sun, 12 Jan 2025 00:00:00 +0000

just a lil guide for my future self when i inevitably forget this again (and it’s probably still wrong oops-)

- Steps:

- Find the commit you want to revert to & copy its hash:

- Return to your open project:

for me, i was working with a locally-cloned copy in VScode, connected to the remote repo’s main branch, and was up to date with all of the changes made.

- Create new remote branch:

open the terminal and run git checkout -b <new-remote-branch> <old-commit-hash>. This will create a new remote branch populated with the project at the time of the commit hash you specified, and switch you to it.

E.g., git checkout -b names-update 4853ecf5765b7174465e604e8fd8bdd5430ea84f.

- Push this new remote branch:

then, simply push this new remote branch with git push origin <new-remote-branch>, and check that it appears on github!

Now you can operate off this new branch, containing the project in a previous commit’s state.

yes… i know this is a very simple thing to do that i only just kinda grasped >.<

PACK files in .git - a rabbit hole

Mon, 23 Dec 2024 00:00:00 +0000

- so, how did we get here? 🙈

git stores all historical changes to a repo in a PACK file inside the hidden .git folder. This allows restoration of previous repo states in the future.

However, if you upload files like binaries, photos or videos, this file gets VERY large, even if you delete them in a future commit.

- enter: `git-filter-repo`

Luckily a tool exists called git-filter-repo that you can download and use (python script) to analyse your PACK file, and filter out any unwanted bits (e.g. file extensions, paths, etc.). This can dramatically reduce the size of the PACK file.

It works in a single command (with the option to point the command to a file defining what to keep/exclude, if preferred). Just download the python script, move it to your working directory (MUST have .git folder, as it will analyze this), and run:

python git-filter-repo.py --analyze

(the use of “python” or similar, and giving the script a .py extension, is necessary sometimes on windows, depending on what shell you’re running the above command in, your PATH configuration etc. - but just think of it as running a script file and passing the “analyze” argument to it)

It then produces a folder with text files showing files/repo paths (historical) and their relative sizes. From here, you can search through and figure out how to filter what you’d like to remove.

When you’ve decided what you’re going to remove and how (path/extension/date etc.), I recommend doing a –dry-run, which will produce two files (the original version and the modified version) and comparing what elements were removed with your filter. For me, using the following command, I went from 6473 lines of committed files to 1428.

python git-filter-repo.py --path 'old-site/audio/' --path 'old-site/photos/' --invert-paths --dry-run --force

(I used –force as I had one untracked change - being moving the git-filter-repo script file itself into the directory - that I didn’t want to push to git)

And to make “the changes” [PERMANENTLY!! CAUTION!!!] remove the --dry-run component of the above command, resulting the following:

python git-filter-repo.py --path 'old-site/audio/' --path 'old-site/photos/' --invert-paths

Run that, and then there you go - it should make the changes to the .git folder in your repo, stripping out the components of the file you filtered and producing a new, (hopefully) smaller PACK file.

Now, it just needs to be pushed to the remote repository with:

git push --all [remote-repo-URL]

- and then…

well, if all things went well, you should have shaved a few KBs/MBs/GBs off your PACK file - well done! grab yourself a cookie, you’ve well and truly earnt it :3

Git on juni's blog ٩(◕‿◕｡)۶

Branching out with a previous commit in a GitHub project

- Steps:

- Find the commit you want to revert to & copy its hash:

- Return to your open project:

- Create new remote branch:

- Push this new remote branch:

PACK files in .git - a rabbit hole

- so, how did we get here? 🙈

- enter: `git-filter-repo`

- and then…

- other helpful links:

Git on juni's blog ٩(◕‿◕｡)۶

Branching out with a previous commit in a GitHub project

- Steps:

- Find the commit you want to revert to & copy its hash:

- Return to your open project:

- Create new remote branch:

- Push this new remote branch:

PACK files in .git - a rabbit hole

- so, how did we get here? 🙈

- enter: git-filter-repo

- and then…

- other helpful links:

- enter: `git-filter-repo`