iwantcoding.com
🔥 Daily 👥 Rooms 🏆 Top Log in Sign up
Next »

Git Summary

By · Reviewed & last updated · Part of Git Tutorial

Wrapping up the git track with what you can ship and where to go next.

What you learned + signed commits setup

EXAMPLE
# Git summary

You can now:

- Reason about the working tree, index, and HEAD
- Use branching strategies (trunk-based or short-lived feature branches)
- Choose merge vs rebase vs cherry-pick deliberately
- Recover almost anything with reflog and bisect
- Clean up history with interactive rebase + autosquash
- Sign commits and tags with SSH or GPG
- Collaborate with CODEOWNERS, protected branches, and required checks
- Operate across GitHub, GitLab, and Bitbucket

# Your next step - signed commits with SSH

# Tell git to sign with SSH
git config --global gpg.format ssh
git config --global commit.gpgsign true
git config --global tag.gpgsign true
git config --global user.signingkey ~/.ssh/id_ed25519.pub

# Verify your local config worked
git commit --allow-empty -m 'test: signed commit'
git log --show-signature -1

# Add the same public key as a 'Signing Key' in GitHub:
# Settings -> SSH and GPG keys -> New SSH key -> Key type: Signing
# Now your commits show 'Verified' on GitHub.

# Enforce on main (recommended):
# Branch protection -> Require signed commits

Why it matters

Git is plumbing more than UI. Once recovery (reflog + bisect) and history-cleaning (rebase + autosquash) are reflexive, the daily work feels safe. Signed commits + protected branches turn a personal tool into a team-grade one.

Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.

Example

Example
# Next: master rebase, hooks, advanced log filters, GitHub Actions.
Try it Yourself »

Discussion

Loading…

Next »