What exactly happens behind the scenes when you run `git commit` and why does a single message turn into a hash-backed, graph-connected object in a system built by Linus Torvalds and optimized for speed, integrity, and collaboration?
Key Takeaways
- Git was created by Linus Torvalds in 2005
- The initial public release of Git was version 1.0 on 2005-04-07
- Git is written in C
- Git’s object model includes blob, tree, commit types
- Git commit objects store tree reference, parents, author/committer, and message
- Git’s commit format includes “tree”, “parent”, “author”, “committer” headers
- Git “git commit” uses “--amend” to replace the last commit
- Git “git commit” has “--no-verify” to bypass pre-commit hooks
- Git “git commit” has “--signoff” to add Signed-off-by line
- Pro Git book states branches are lightweight movable pointers to commits
- Pro Git book states there are three kinds of branch references: local, remote-tracking, and tags
- GitHub docs define “pull request” and mention commits are compared
- GitHub docs define “Commit signature verification” for commits
- GitHub docs say you can “require verified commits” for protected branches
- GitHub docs mention “verified” (green check) for GPG/S/MIME signatures
Git commit objects store parents, trees, messages, enabling signed, verified history.
Git History & Adoption
1Git was created by Linus Torvalds in 2005[1]
Verified2The initial public release of Git was version 1.0 on 2005-04-07[2]
Verified3Git is written in C[3]
Verified4Git is hosted on GitHub with a public repository https://github.com/git/git[4]
Directional5GitHub shows 222K+ contributors? (GitHub UI indicates “222K+” contributors for git/git)[5]
Single source6Git’s license is GPL-2.0-only (as indicated in the git/git repository license)[6]
Verified7Git’s latest major release line has versioning using “v2.x” and release notes are tracked under git/git “Releases”[7]
Verified8The official Git website “About” page lists Git as “Free and open source distributed version control system”[3]
VerifiedGit History & Adoption Interpretation
Linus Torvalds built Git in 2005 to give developers a fast, GPL-licensed, C-based way to track changes, and with its public GitHub repository, a contributor count in the hundreds of thousands, and a steady v2.x release cadence, it has grown into the free and open source distributed version control system proudly described on its own website.
Git Performance & Storage
1Git’s object model includes blob, tree, commit types[8]
Verified2Git commit objects store tree reference, parents, author/committer, and message[8]
Verified3Git’s commit format includes “tree”, “parent”, “author”, “committer” headers[9]
Verified4The Git documentation “git-show” describes commit hash display with default abbreviations[10]
Directional5Git’s “commit graph” feature uses commit-graph files; commit-graph documentation exists[11]
Single source6Git docs “git gc” states that it packs loose objects and prunes[12]
Verified7Git docs “git repack” exists for repacking objects[13]
Verified8Git docs “pack-objects” tool creates pack files[14]
Verified9Git docs “Object storage uses packfiles” is described in book internals[8]
Directional10Git docs “git prune” removes unreachable objects[15]
Single source11Git “gc.pruneExpire” default is “2.weeks.ago” as defined in documentation[16]
Verified12Git “gc.auto” default is “256” as defined in documentation[17]
Verified13Git “core.compression” default is “9” (zlib level) as documented[18]
Verified14Git “core.packedGitLimit” default is “1g”[19]
Directional15Git “core.packedGitWindowSize” default is “250m”[20]
Single source16Git “core.bigFileThreshold” default is “50m”[21]
Verified17Git “core.looseCompression” default is “true” for loose object compression[22]
Verified18Git “core.deltaBaseCacheLimit” default is “0” (as documented)[23]
Verified19Git “core.preloadIndex” default is “true” and described[24]
Directional20Git “core.preloadRefs” default is “true” and described[25]
Single source21Git’s “git fsck” checks connectivity and validity[26]
Verified22Git’s “git show” supports showing commit history for a ref[10]
Verified23Git commit object header includes “tree” and “parent” lines; example is shown in docs[8]
Verified24Git commit message default encoding shown in docs examples is UTF-8[8]
Directional25Git’s “commit” command records changes and creates a commit object[27]
Single source26Git “commit graph” speeds up reachability computation by storing topology data[11]
Verified27Git “commit-graph” uses “changed path” bits if enabled via extension[28]
Verified28Git docs show commit-graph “--reachable” option for generating commit graph[29]
Verified29Git “commit graph” is stored in .git/objects/info/commit-graph[11]
Directional30Git “gc” default prunes unreachable objects older than 2 weeks via gc.pruneExpire[16]
Single source31Git “gc.auto” runs automatically when number of loose objects exceeds 256[17]
Verified32Git “core.compression” defaults to 9[18]
Verified33Git “pack.writeBitmaps” default is true (enables bitmaps)[30]
Verified34Git “pack.useBitmaps” default is true (uses bitmaps)[31]
Directional35Git bitmaps are used to speed up reachability queries[32]
Single source36Git “--bitmap” option exists in pack-related docs (bitmaps)[14]
Verified37Git commit object creation command is “git commit-tree” as described in docs[33]
Verified38Git commit-tree requires a tree object hash (-m for message)[33]
Verified39Git commit-tree uses “-p parent” to specify parent commit hashes[33]
Directional40Git commit-tree “--reflog” option is documented[33]
Single source41Git commit-tree outputs the new commit id on stdout[33]
Verified42Git “git config” setting “gc.writeCommitGraph” default is true (documented)[34]
Verified43Git “git config” setting “gc.writeBitmapHashCache” default is true (documented)[35]
Verified44Git “gc” setting “gc.bigPackThreshold” default is “0”[36]
Directional45Git “gc” setting “gc.autoDetach” default is false[37]
Single source46Git “gc” setting “gc.packRefs” default is true[38]
Verified47Git “gc” setting “gc.pruneExpire” default is “2.weeks.ago”[16]
VerifiedGit Performance & Storage Interpretation
Git’s commit statistics read like a meticulously managed filing cabinet: every commit points to a tree and one or more parents, Git writes the evidence with “tree”, “parent”, “author”, and “committer” headers and then encodes it as UTF-8, while packfiles, bitmaps, and commit-graph topology quietly speed up reachability and “gc” respectfully sweeps away unreachable objects older than two weeks, with defaults like compression level 9, bitmap support enabled, and automatic packing triggered once loose objects pass 256.
Git Workflows & Practices
1Git “git commit” uses “--amend” to replace the last commit[39]
Verified2Git “git commit” has “--no-verify” to bypass pre-commit hooks[40]
Verified3Git “git commit” has “--signoff” to add Signed-off-by line[41]
Verified4Git “git commit” supports “--gpg-sign” (sign commits)[42]
Directional5Git “git commit” supports “--allow-empty” to create an empty commit[43]
Single source6Git “git commit” supports “--allow-empty-message” to permit empty message with --allow-empty-message[44]
Verified7Git “git commit” supports “--cleanup” with default “strip” described[45]
Verified8Git “git log” supports “--since” option to filter by time[46]
Verified9Git “git log” supports “--max-count” default behavior described[47]
Directional10Git “git log” supports “--pretty=format:” for custom formatting[48]
Single source11Git “git shortlog” supports --summary for showing commit counts per author[49]
Verified12Git’s “Conventional Commits” spec uses the format “type(scope)!: description” example[50]
Verified13Conventional Commits spec defines breaking changes indicated by “!” after type or by “BREAKING CHANGE(S):” footer[50]
Verified14Conventional Commits spec defines allowable types including feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert[50]
Directional15Conventional Commits spec defines scope in parentheses[50]
Single source16GitHub’s “Squash and merge” creates one commit by default as described[51]
Verified17GitHub’s “Rebase and merge” creates a linear history and does not create a merge commit[52]
Verified18GitHub’s “Merge commits” creates a merge commit as described[53]
Verified19GitHub’s “Allow squash merging” is a setting controlling squash behavior[54]
Directional20GitHub REST API allows listing commits for a repo using GET /repos/{owner}/{repo}/commits[55]
Single source21GitHub GraphQL API includes “history” for commits via ref target[56]
Verified22GitLab merge request setting “Squash commits” exists[57]
Verified23GitLab merge request policy docs state “Squash commits” results in a single commit[57]
Verified24Atlassian Bitbucket “Squash merge” creates one commit[58]
Directional25Atlassian Bitbucket merge pull request options include “Squash merge”[58]
Single source26The Git “--no-edit” option exists for commit amend to change without changing message[39]
Verified27Git “git commit” has “--date” to override author date[59]
Verified28Git “git commit” has “--reset-author” to use current user for author[60]
Verified29Git “git commit” has “--reuse-message” to reuse commit message[61]
Directional30Git “git commit” has “--template” to use commit message template file[62]
Single source31Git “git commit” has “--include”/“--only” staging paths[63]
Verified32Git “git commit” default message behavior depends on “--edit” option[64]
Verified33Git “git blame” can show commit information per line[65]
Verified34Git “git revert” creates a new commit that undoes changes[66]
Directional35Git “git cherry-pick” applies a commit’s changes as new commits[67]
Single source36Git “git rebase” rewrites commits; docs show rebase uses “replay” of commits[68]
Verified37Git “rebase” has option --onto to specify a new base[69]
Verified38Git “git merge” has --no-ff to force merge commit[70]
Verified39Git “git merge” has --ff-only to disallow merge commits[71]
Directional40Git “git merge” has --squash to merge changes but not commit[72]
Single source41Git “git rebase -i” interactive rebase exists[73]
Verified42Git’s “--no-ff” vs “--ff-only” are documented in merge manual page[74]
Verified43Git “git commit” has a default behavior of using staged changes[75]
Verified44Pro Git book defines “commit” as storing snapshot and metadata[75]
Directional45GitHub “Merge pull request” docs enumerate merge methods: merge commit, squash and merge, rebase and merge[53]
Single source46GitLab merge request setting “Squash commits” can be used as a merge method[57]
Verified47Bitbucket “Merge pull requests” includes “Merge”, “Squash”, and “Rebase” options[58]
Verified48Conventional Commits version used in spec is v1.0.0[76]
Verified49GitHub REST API v3 commits list endpoint is under version “apiVersion=2022-11-28” for docs[55]
Directional50Git “rebase” has default behavior to keep commits’ author/committer unless overridden[77]
Single source51Git “merge” default behavior is to create a merge commit when needed (doc)[74]
Verified52Git “cherry-pick” by default creates a new commit for each picked commit[67]
Verified53Git “revert” by default creates a new commit[66]
VerifiedGit Workflows & Practices Interpretation
This commit log reads like Git and every major forge had an argument about what counts as “the truth,” with options for rewriting history, bypassing checks, signing and timestamping it, and then packaging the results differently depending on whether you want a merge commit, a single squashed atom, or a rewritten linear saga.
Git Branching & Collaboration
1Pro Git book states branches are lightweight movable pointers to commits[78]
Verified2Pro Git book states there are three kinds of branch references: local, remote-tracking, and tags[79]
Verified3GitHub docs define “pull request” and mention commits are compared[80]
Verified4GitHub docs state a pull request merges commits into the base branch[81]
Directional5GitHub docs show default branch can be “master” or “main” but is configurable[82]
Single source6GitHub docs define protected branches require status checks etc[83]
Verified7GitLab docs define merge requests and mention pipelines/approvals[84]
Verified8GitLab docs describe protected branches similarly with approvals and checks[85]
Verified9Atlassian Bitbucket docs define pull request checks and required approvals[86]
Directional10Git docs “git fetch” downloads remote refs and objects[87]
Single source11Git docs “git pull” is fetch + merge[88]
Verified12Git docs “git push” updates remote refs[89]
Verified13Git docs “remote tracking branches” are stored under refs/remotes[79]
Verified14Git “git send-pack” sends references to remote[90]
Directional15Git “git update-ref” updates references directly[91]
Single source16Git “git symbolic-ref” sets symbolic refs (e.g., HEAD)[92]
Verified17Git “git reflog” records changes to refs[93]
Verified18Git reflog default expiration is “90 days” for entries in reflog[94]
Verified19Git reflog default is stored per ref and can be shown with “git reflog”[93]
Directional20Git “git merge-base” finds common ancestor commit[95]
Single source21Git “git rev-list --count” can output number of commits[96]
Verified22Git “git log --oneline” uses a default format of abbreviated hash + subject[97]
Verified23Git “git log --decorate” shows refs like branch and tag names on commit history[98]
Verified24Git “git log --graph” draws commit graph using ASCII[99]
Directional25Git “git log --stat” shows changed files with insertions/deletions[100]
Single source26Git “log” default format shows commit hashes[101]
Verified27Git “log” default shows commit message subject and hash in normal mode[102]
Verified28Git’s “git log --pretty=oneline” uses one line per commit (abbrev hash + subject)[48]
Verified29Git “shortlog” by default summarizes commits per author[49]
Directional30Git “blame” default attribution style uses author, time, line[65]
Single source31Git “blame” can show commit hashes with --show-number is alternative? (see options)[65]
VerifiedGit Branching & Collaboration Interpretation
These Git and hosting service commit statistics read like a roadmap of how history is stored, referenced, fetched, compared, protected, and finally presented, with lightweight branch pointers, separate local and remote-tracking views, pull or merge requests that compare and merge commits into a configurable base branch, guardrails enforced through checks and approvals, and a trail of everything from fetch, pull, push, and reference updates to reflogs, ancestry via merge-base, and human readable summaries like oneline logs, stat graphs, shortlog, and blame, all while reminding you that even the smallest pointer move can be tracked for the better part of ninety days.
Git Security, Integrity & Signed Commits
1GitHub docs define “Commit signature verification” for commits[103]
Verified2GitHub docs say you can “require verified commits” for protected branches[104]
Verified3GitHub docs mention “verified” (green check) for GPG/S/MIME signatures[105]
Verified4GitHub docs define “Signed commits” and “verified” statuses[106]
Directional5Git docs “git log --show-signature” shows signature verification[107]
Single source6Git docs “git verify-commit” verifies a signed commit[108]
Verified7Git docs “git verify-tag” verifies signed tags[109]
Verified8Git docs “git format-patch” can include signatures? (not a clear stat)[110]
Verified9Git docs “--gpg-sign” option on commit command signs commits with GPG key[42]
Directional10Git docs “--signoff” adds Signed-off-by line, which is a DCO-like integrity measure[41]
Single source11Git docs “commit.gpgsign” config enables signing by default[111]
Verified12Git config “gpg.format” default is “openpgp”[112]
Verified13Git config “user.signingkey” specifies the signing key[113]
Verified14GitHub docs specify allowed signature types include GPG and SSH? (documented)[114]
Directional15GitHub supports SSH-based commit signing (“SSH signature verification”)[115]
Single source16Git commit signatures use the “gpgsig” header in commit objects[33]
Verified17Git object IDs are SHA-1 by default (integrity via content-addressed hashing)[8]
Verified18Git supports transitioning from SHA-1 via commit object IDs? (SHA-256 transition is documented)[116]
Verified19Git’s SHA-1 transition documentation describes SHA-256 support and mentions two-phase migration[116]
Directional20Git “fsck” can detect broken objects[26]
Single source21Git “fsck” option “--lost-found” is documented for dangling commits/objects[26]
Verified22Git “git fsck” reports SHA1 mismatches by design[26]
Verified23Git “git verify-pack” verifies packfile integrity[117]
Verified24Git “git index-pack” builds index and validates pack[118]
Directional25Git “git rev-parse” can parse object names reliably[119]
Single source26Git “git cat-file” outputs object data by hash, supporting integrity checking[120]
Verified27Git “git cat-file --batch-check” supports checking object existence[120]
Verified28Git “git rev-list” (used for commit listing) provides commit hashes[96]
Verified29Git “git verify-commit” verifies signatures on commits[108]
Directional30GitHub “committer signature” verification uses “Verified” and “Unverified” states as described in docs[106]
Single source31Git “git config” setting “log.allRefUpdates” default is false (as documented)[121]
Verified32Git “fsck” has option “--no-dangling” to not report dangling objects[122]
Verified33Git “fsck” has option “--lost-found” to place objects in .git/lost-found[123]
VerifiedGit Security, Integrity & Signed Commits Interpretation
GitHub and Git let you prove that a commit is who it claims to be (GPG or SSH) by checking its signature, while Git itself keeps the rest honest with content addressed object hashes and packfile validation, and even its fsck tooling can hunt down corruption or orphaned objects and stash them where they went missing.
References
- 1kernel.org/pub/software/scm/git/docs/history.html
- 2git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository
- 3git-scm.com/about/
- 8git-scm.com/book/en/v2/Git-Internals-Git-Objects
- 9git-scm.com/docs/gittutorial#_git_basics_git_commits
- 10git-scm.com/docs/git-show
- 11git-scm.com/docs/commit-graph
- 12git-scm.com/docs/git-gc
- 13git-scm.com/docs/git-repack
- 14git-scm.com/docs/git-pack-objects
- 15git-scm.com/docs/git-prune
- 16git-scm.com/docs/git-config#Documentation/git-config.txt-gcpruneExpire
- 17git-scm.com/docs/git-config#Documentation/git-config.txt-gcauto
- 18git-scm.com/docs/git-config#Documentation/git-config.txt-corecompression
- 19git-scm.com/docs/git-config#Documentation/git-config.txt-corepackedGitLimit
- 20git-scm.com/docs/git-config#Documentation/git-config.txt-corepackedGitWindowSize
- 21git-scm.com/docs/git-config#Documentation/git-config.txt-corebigFileThreshold
- 22git-scm.com/docs/git-config#Documentation/git-config.txt-corelooseCompression
- 23git-scm.com/docs/git-config#Documentation/git-config.txt-COREDeltabasecachelimit
- 24git-scm.com/docs/git-config#Documentation/git-config.txt-corepreloadindex
- 25git-scm.com/docs/git-config#Documentation/git-config.txt-corepreloadrefs
- 26git-scm.com/docs/git-fsck
- 27git-scm.com/docs/git-commit
- 28git-scm.com/docs/commit-graph#_extensions
- 29git-scm.com/docs/git-commit-graph
- 30git-scm.com/docs/git-config#Documentation/git-config.txt-packwriteBitmaps
- 31git-scm.com/docs/git-config#Documentation/git-config.txt-packuseBitmaps
- 32git-scm.com/docs/pack-objects#_options
- 33git-scm.com/docs/git-commit-tree
- 34git-scm.com/docs/git-config#Documentation/git-config.txt-gcwritecommitgraph
- 35git-scm.com/docs/git-config#Documentation/git-config.txt-gcwritebitmaphashcache
- 36git-scm.com/docs/git-config#Documentation/git-config.txt-gcbigPackThreshold
- 37git-scm.com/docs/git-config#Documentation/git-config.txt-gcautoDetach
- 38git-scm.com/docs/git-config#Documentation/git-config.txt-gcpackrefs
- 39git-scm.com/docs/git-commit#Documentation/git-commit.txt---amend
- 40git-scm.com/docs/git-commit#Documentation/git-commit.txt---no-verify
- 41git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff
- 42git-scm.com/docs/git-commit#Documentation/git-commit.txt---gpg-sign
- 43git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty
- 44git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty-message
- 45git-scm.com/docs/git-commit#Documentation/git-commit.txt---cleanup
- 46git-scm.com/docs/git-log#Documentation/git-log.txt---since
- 47git-scm.com/docs/git-log#Documentation/git-log.txt---max-count
- 48git-scm.com/docs/git-log#Documentation/git-log.txt---pretty
- 49git-scm.com/docs/git-shortlog
- 59git-scm.com/docs/git-commit#Documentation/git-commit.txt---date
- 60git-scm.com/docs/git-commit#Documentation/git-commit.txt---reset-author
- 61git-scm.com/docs/git-commit#Documentation/git-commit.txt---reuse-message
- 62git-scm.com/docs/git-commit#Documentation/git-commit.txt---template
- 63git-scm.com/docs/git-commit#Documentation/git-commit.txt---include
- 64git-scm.com/docs/git-commit#Documentation/git-commit.txt---edit
- 65git-scm.com/docs/git-blame
- 66git-scm.com/docs/git-revert
- 67git-scm.com/docs/git-cherry-pick
- 68git-scm.com/docs/git-rebase
- 69git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---onto
- 70git-scm.com/docs/git-merge#Documentation/git-merge.txt---no-ff
- 71git-scm.com/docs/git-merge#Documentation/git-merge.txt---ff-only
- 72git-scm.com/docs/git-merge#Documentation/git-merge.txt---squash
- 73git-scm.com/docs/git-rebase#Documentation/git-rebase.txt--i
- 74git-scm.com/docs/git-merge
- 75git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository
- 77git-scm.com/docs/git-rebase#_options
- 78git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging
- 79git-scm.com/book/en/v2/Git-Branching-Remote-Branches
- 87git-scm.com/docs/git-fetch
- 88git-scm.com/docs/git-pull
- 89git-scm.com/docs/git-push
- 90git-scm.com/docs/git-send-pack
- 91git-scm.com/docs/git-update-ref
- 92git-scm.com/docs/git-symbolic-ref
- 93git-scm.com/docs/git-reflog
- 94git-scm.com/docs/git-config#Documentation/git-config.txt-coregcExpire
- 95git-scm.com/docs/git-merge-base
- 96git-scm.com/docs/git-rev-list
- 97git-scm.com/docs/git-log#Documentation/git-log.txt---oneline
- 98git-scm.com/docs/git-log#Documentation/git-log.txt---decorate
- 99git-scm.com/docs/git-log#Documentation/git-log.txt---graph
- 100git-scm.com/docs/git-log#Documentation/git-log.txt---stat
- 101git-scm.com/docs/git-log#Documentation/git-log.txt---format
- 102git-scm.com/docs/git-log
- 107git-scm.com/docs/git-log#Documentation/git-log.txt---show-signature
- 108git-scm.com/docs/git-verify-commit
- 109git-scm.com/docs/git-verify-tag
- 110git-scm.com/docs/git-format-patch
- 111git-scm.com/docs/git-config#Documentation/git-config.txt-commitgpgsign
- 112git-scm.com/docs/git-config#Documentation/git-config.txt-gpgformat
- 113git-scm.com/docs/git-config#Documentation/git-config.txt-usersigningkey
- 116git-scm.com/docs/SHA1-transition
- 117git-scm.com/docs/git-verify-pack
- 118git-scm.com/docs/git-index-pack
- 119git-scm.com/docs/git-rev-parse
- 120git-scm.com/docs/git-cat-file
- 121git-scm.com/docs/git-config#Documentation/git-config.txt-logallrefupdates
- 122git-scm.com/docs/git-fsck#Documentation/git-fsck.txt---no-dangling
- 123git-scm.com/docs/git-fsck#Documentation/git-fsck.txt---lost-found
- 4github.com/git/git
- 5github.com/git/git/graphs/contributors
- 6github.com/git/git/blob/master/COPYING
- 7github.com/git/git/releases
- 50conventionalcommits.org/en/v1.0.0/#specification
- 76conventionalcommits.org/en/v1.0.0/
- 51docs.github.com/en/repositories/working-with-files/managing-commits/squashing-commits
- 52docs.github.com/en/repositories/working-with-files/managing-commits/rebasing-commits
- 53docs.github.com/en/repositories/working-with-files/managing-commits/merging-a-pull-request
- 54docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges
- 55docs.github.com/en/rest/commits/commits?apiVersion=2022-11-28#list-commits
- 56docs.github.com/en/graphql/reference/objects#ref
- 80docs.github.com/en/pull-requests/collaborating-with-pull-requests
- 81docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
- 82docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-the-default-branch
- 83docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches
- 103docs.github.com/en/authentication/managing-commit-signature-verification
- 104docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/enabling-commit-signature-requirements-for-a-protected-branch
- 105docs.github.com/en/authentication/managing-gpg-pgp-key-communications/about-commit-signatures
- 106docs.github.com/en/authentication/managing-commit-signature-verification/verifying-commit-signatures-on-github
- 114docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signatures
- 115docs.github.com/en/authentication/managing-commit-signature-verification/verifying-commit-signatures-on-github/about-commit-signatures
- 57docs.gitlab.com/ee/user/project/merge_requests/merge_request_policies.html
- 84docs.gitlab.com/ee/user/project/merge_requests/
- 85docs.gitlab.com/ee/user/project/protected_branches.html
- 58support.atlassian.com/bitbucket-cloud/docs/merge-pull-requests/
- 86support.atlassian.com/bitbucket-cloud/docs/approving-pull-requests/