Or the Mullvad browser, Mullvad’s fork of FF with zero ads with help from the Tor project.

I would advocate for using each tool, where it makes sense, to achieve a more intelligible graph. This is what I’ve been moving towards on my personal projects (am solo). I imagine with any moderately complex group project it becomes very difficult to keep things neat.

In order of expected usage frequency:

1. Rebase: everything that’s not 2 or 3. keep main and feature lines clean.
2. Merge: ideally, merge should only be used to bring feature branches into main at stable sequence points.
3. Squash: only use squash to remove history that truly is useless. (creating a bug on a feature branch and then solving it two commits later prior to merge).

History should be viewable from log --all --decorate --oneline --graph; not buried in squash commits.

My town too OP. All the trendy roasters like the fruity floral notes of the light roasts but i can’t its like drinking stomach bile.

Cool now I can actually check it out. Tried to previously but my connection failed about an hour into the clone. --depth=1 --shallow-submodules --recurse-submodules should really be given its own command in git. Not really sure why’d they choose MS as their host though.

It reduces the probability that a drive by scanner is going to detect a vulnerable service. Camouflage isn’t a guarantee that you aren’t going to be sighted on a battlefield, but it’s still a good idea to reduce the probability of becoming a target in whatever ways you can.