I’ve edited this post and linked to the original on Mastodon.

You have to expand the image to its full size. Thumbnail images are downscaled so they use less data.

More like “don’t fuck around but find out anyway”.

Commit -a isn’t easy?

Squashing is easy too, though no, there isn’t a “squash all” option, unless you’re working in a feature branch and check out master and git merge --squash branch: graphite.dev/guides/git-merge-squash

I’m sure there’s a way to commit to another branch without having it checked out, but that just sounds like a recipe for trouble.

And I have no idea how you’d manage to not have different ssh keys per user. You shouldn’t be reusing keys across accounts to begin with.

commit to other branch

‘cherrypick’

I just learned git bisect from https://ohmygit.org/! You run it, then checkout other commits all over the project, and mark them with git bisect good or git bisect bad. Then it paints all commits that led to the good one as good, and all the ones after the bad one as bad, so you just keep narrowing your window by playing checkout Jezzball until there’s only one commit left: the one that introduced the bad state.

You’re gonna love this then:

alias gl='git log --graph --abbrev-commit --no-decorate --date=format:'\''%Y-%m-%d %H:%M:%S'\'' --format=format:'\''%C(8)%>|(16)%h  %C(7)%ad  %C(8)%<(16,trunc)%an  %C(auto)%d %>|(1)%s'\'' --all'

I have a whole rc file full of shortcuts like this for Git and Docker.

git-scm.com/book/en/v2

Madness!

Love lazygit, am I better or worse a git now? Idk but I’m doing it much faster

You dropped –force

Looking great. Thanks.

Every time.

git blame