Git

“I've been using Fossil(and Git) since about the same time(late 2000s)”

“Its way of working with git worktrees exclusively is something I was already doing”

“the server only stores the public key (as a plaintext file in git)”

“But then we moved to git and only stuff that had a designated owner got moved from cvs/svn to git”

“I bisected the game code with git, went back two months, and everything was broken.”

“when we switched from SVN to git I had to show ROI”

“At Fortinet we migrated our SVN repositories to git and ran into a ton of issues”

“moving a massive, complex SVN repository into multiple separate Git repositories”

“We've also done cvs -> svn -> git. All the commits have survived migration.”

“At the time, I had about a week of experience with git! And here I was, operating what was expected to be a very popular open repo”

“After 6 months I had confidence and the training of everyone was complete and we switched over.”

“Permissions handled at the git level.”

“so we switched to deleting branches upon merge, discarding some git history along with that”

“code that I personally wrote from the design, the implementation the refactoring, etc from the first git init”

“we give the parser byte blobs from git, also using git ls-files to 'stat' the files”

“with all the smarts living in Git next to the code it was building”

“We have a custom CI job that trawls git and figures out which projects changed”

“We're a game studio with less technical staff using git (art and design) so we use hooks to break some commands that folks usually mess up.”

“I've been using their git diff/checkin tools built into RubyMine since I started with git. Going on about 12-13 years now.”

“I've been using a git repo for dotfiles but having them automatically cleanup on disconnect is clever.”

“The docker container doesn't have git credentials, so claude code can see git history etc and do local git ops”

“I came up with this workflow that I've been using for almost a year now and have been extremely productive”

“all Git submodules are checked out”

“Surprised something like it hasn't landed in upstream git.”

“Open up a new Claude window and then use a git worktree with the Execute Plan command.”

“it takes minutes up to even hours for some Git operation”

“The company I work at is using the same exact branching strategy I introduced when we moved to git”

“we run agents or any LLMs with 'filesystem powers' in a VM, with a git repo and saved rollback states.”

“We use Git for source control but have a CI/CD solution that is built in house.”

“a function in `git bundle create` that checks for duplicate references... The patch was accepted, but we also backported fix”

“Those we keep in Excel in Git, so that business users can edit / maintain them.”

“When my then-employer first stated using git, I managed to convince them to set up Gerrit”

“we migrated to git in 2016”

“all have their own Git branch with whatever Helm, OpenTOFU, etc.”

“The whole deployment process is done in a bash script which uses the git hash for versioning”

“I have been using Git for 15 years and am one of the earliest GitHub users, and I have not regularly used Git for nearly anything, in any job”

“I was always suspicious that git pull just works even if I rebased the branch remotely”

“for certain repos I have to revert to git.”

“a builder that can run git and mvn and npm to automatically sync up and build a collection of Java and Javascript projects”

“even when I periodically go back to using git (for older projects I don't have a jj clone out for)”

“When I first started at my current job some twelve years ago we would git pull from each other's machines directly.”

“Setting up git is the easy part. We all used it.”

“The last time I had to decide for a new team, mercurial and git were the obvious options. I went with git”

“I also once butchered the result of 40 hours of work through a loose git history rewrite.”

“git and Nix are almost the same data structure if you start poking around in .git”

“then we switched to Git because of the cloud thing”

“Then we moved to git from svn but kept everything else the same.”

“I squash intermediate commits between change sets, and try to only reveal atomic change sets on any shared branch.”

“sometimes I have to git mergetool quite big patches with many conflicts”

“I've been using git for 10 years and still feel like an amateur.”

“I use the obsidian git and org plugin to sync, view, and edit my org documents.”

“We opted for git submodules because go modules hate CalVer”

“So when we switched to Git, the CLI paradigm just seem unfamiliar to me.”

“after we switched to git there was no difference in productivity”

“I still use git like a fancy subversion, just with multiple repositories”

“We switched a year or so ago to use git sparse checkout that was released in 2.25.”

“I use git commit --amend to build up a single commit as I go.”

“In the beginning, I set the goal to version the whole process in git.”

“I also used git to manage changes.”

“all the tooling and integrations are git based so we switched.”

“we switched to Git at time of Mercurial 2.1 (I said it was long time ago)”

“pnpm also allows us to use features like git sparse-checkout because we can be confident there are no implicit dependencies”

“When we switched to Git we decided that we liked code reviews and wanted to make them part of merging to develop.”

“I remember the `git push` ended up taking a while.”

“One "back up" solution I did was dump tables to text - commit the diff in git.”

“I've been using Tor to provide remote access to my private git repos while traveling and working remotely.”

“I learned a lot of things about Git from this project.. so yeah, just be careful is all in certain architectural contexts.”

“they can write code and commit to our Git repository as much as they want”

“then I add my one line of code to the git repo to point to the new spreadsheet”

“The squash commits are some of the worst commits for finding out why a weird design decision was made”

“try to reproduce and the `git bisect` to find the culprit. Not to blame but just to figure out what's wrong”

“I wrote a simple script that scrubbed secrets from the commit history using git fast-export and git fast-import.”

“I've occasionally used git-revert, but it's usually when I'm half-expecting to revert it but want to see how it behaves in prod.”

“We use git+markdown for my software team's documentation.”

“I've been using the stuff that comes with the git-scm.com distribution of git for windows.”

“I've always just used git from the command line”

“The fact that git is centralized or decentralized crosses our minds precisely zero times per week.”

“In Brazil, every package is its own git repo and it's very straightforward to just list the git history of a package”

“On my team, we will open a PR with a logical set of commits. As reviews are posted, we will address those comments by using fixup! or squash! commits”

“If it's shit I can "git checkout -- ." and walk away.”

“We migrated from SVN to Git at the beginning of 2018, and spent a lot of time getting the revision history migrated.”

“We switched from SVN to Git about a year and a half ago.”

“I then lead another whole project to migrate the whole company to Git and Ansible for deploys.”

“I've been using git for going on ten years.”

“We use git hooks to tie issues and commits together.”

“the git commit message are often the best place to warn future programmers of pitfalls”

“since I'd been using git to sync pass between my phone and computer (the recommended setup)”

“listens to every git push my team makes to launch a code recompile/redeploy”

“From the git branches, commits to a feature branch build and deploy to a sandbox env.”

“We have some additional infrastructure for staff: our LDAP directory, an IdP ... Git for code”

“abbr -a gp 'git push' abbr -a k kubectl abbr -a n 'npm run' abbr -a y yarn abbr -a m make”

“it works like a normal git repository so you get all your synchronization”

“I've been using it for almost everything, and still don't really understand what it is actually doing.”

“records things like git revision info and deployer name in the annotations”

“his last 4 commits on master are at the following time”

“This is why we built and manage our own git servers internally.”

“I have a lovely git repository of code.”

“there aren't many things we can't do with the tools available: Slack, Google Docs, email, git, etc.”

“Then after about a year of mercurial we switched to git and our brains had adapted.”

“at my current workplace, we use the following workflow: Master, main, and feature branches.”

“I've been using the same note take system for the last two years.”

“makes Mercurial easy to use for this (somewhat) hardened Git user”

“when I type `git revert <TAB>` I get something like 0a129475 (Replace opts.stdout with opts.to_stdout)”

“even rebases become safe and friendly. Its definitely a git client on a league of its own.”

“we gave up and only migrated the current checkin to git, but most projects pull out the full history and all branches with no trouble.”

“git push takes a few seconds, but bearable.”

“Currently we do pay for our Git hosting because of our requirements”

“A coworker suggested we use the same desktop version of git and we switched, no questions asked.”

“A coworker(10 years my senior) suggested we use the same desktop version of git and we switched, no questions asked.”

“our using of GPG + Keybase + Git + Hub for commit signing + KBFS”

“Git+JSON to store content.”

“Now I push to git more often.”

“I did not use AWS but just Bitbucket, git pull and the site is published”

“we switched the entire Visual Studio repo to git, hosted on Visual Studio Team Services, after we shipped Visual Studio 2015.”

“I actually had this happen once when I was running a small filesystem based git server.”

“Then we'd write code and check it in via git as with any other project.”

“we switched to hosted Confluence, JIRA, BitBucket/git.”

“we all knew we SHOULDN'T have been doing things like generate shell script execution and using git to provision on production boxes”

“They use git by the way and I have been using it for a while now.”

“I use the following to jump from merge to merge when bisecting (we use pull requests as our main "clean history" management).”

“clicking one deploy button in our version control system (which does a "git pull" on the web servers)”

“I tell developers to always rebase local work before committing... what the author describes is fairly close to what I've been using in a number of companies now for the last 9 years”

“We do some horrible things to git for the rest of our system too.”

“we switched to git only in December 2011, before that you would need to look at the ChangeLog.”

“It's basically a wiki using ruby brick and git to serve the md pages.”

“git and go are the only two commands I type while writing go code.”

“The pre-commit workflow doesn't work too well with git, since the review happens before you upload the code.”

“since git doesn't log file moves you can run into "broken" history for a file”

“I've been using git for years at this point, so I'm glad to leverage my existing skill.”

“we use git and developers can't commit to the master branch. They commit to their own branch, the build system builds/tests that branch”

“I also think it predates our switching to git from subversion...”

“The switch to Git happened one day before we open sourced on June 17, 2008”

“Code lives in Git as well via GitFileTree.”

“We recently switched ... from deployment on ubuntu servers via 'git pull' managed with supervisord to docker/coreos/fleet”

“When we migrated over from CVS to git, we installed an instance of GitLab.”

“Haxe, git, mercurial, FlashDevelop, Java, etc...”

“The value of ubiquity exceeded the value of our previous preferences.”

“git had more support/momentum so we switched.”

“researching and working with ... using git/github more efficiently”

“I've been using Git for years.”

“I can edit code in one pane, manage my git repository in another”

“# Make the repo git init git add . && git commit -m 'First!'”

“our own hosted git and hg”

“DCVS: git. Our repos are hosted on Github”

“Bitbucket/Git - code repository”

“I rarely need the git command line with IDEA.”

“makes git diffs really easy and launches in a second on my Mac. It also provides integration with services like git”

“I'll be glad to save another 1 character with 1.8.5.”

“At work, my Git repos are exclusively C# and I've been using SemanticMerge for resolving conflicts to good effect.”

“most of the developers are simply much more used to git, and so we use git.”

“So far, there are FEW benefits i see to using, or switching to, GIT”

“i started a place they used git, i started learning it but nobody already there knew a damned thing about it”

“All my work is via Git. So in my team we use GitHub for our normal projects (pay per project)”

“We use branches a lot at our startup. Typically our workflow goes as follows: git checkout master”

“I've been using Git for all my version control since 2008”

“The company I work for has at least 50 projects all using Git and the only time we use --force is when we have to clean up a major mistake”

“If you deploy from git, like many of us do, and you're in the middle of pulling down dependencies from github”

“I can't say that I've ever had a problem with accidentally running commands in my top-level repo despite many years of running it under git”

“On my git.git repository, running time __git_ps1 takes about .085s.”

“The recipe looks at each of our git repos, finds ones that have been updated on the appropriate production branch”

“we moved to using Git to manage our Keepass DB”

“by the way, `git diff --no-index` also works like a generic diff utility on any two files.”

“even though we use Git, I still have the habit of making full copies of directories every so often”

“I have used it for about a year and there's still plenty of features I haven't ever had to use”

“At the beginning, I even don't know how to use the "git" to manage my repository. It really takes me some days to learn it.”

“We use git. We're agile. We iterate.”

“I check-in on my dev box and run a remote script to deploy straight from the Git repo.”

“drush up feature_name git commit -a”

“how we stored our Git repositories on the backend changed dramatically during the move from virtualized to bare metal”

“we use Git (@ Github) for our repositories, and TeamCity for CI.”

“Check out is more than twice slower on Windows (we use git).”

“accidentally type "git status" in the VM instead of the host machine”

“We use subversion, git and mercurial internally.”

“I went to HG but then gave Git another attempt because I didn't like feeling defeated.”

“We use git at my workplace without branching, and we practice continuous deployment.”

“I've only been using version control (Git is the only system I've tried) for about 4 months or so”

“Mine uses the output of `git status --porcelain` to get the changed files, and writes them to a temporary directory with `git show`.”

“we use chef with the Opscode Platform and a git workflow for our chef repo”

“My work legal department decided it was a conflict of interest (we use Git)”

“my work legal department decided it was a conflict of interest (we use Git) and forbid me from working on it anymore.”

“Push to a GIT server, we have a branch called 'live', then we run a script on the servers that pull down the deploy branch.”

“we use Git for all the book revisions (both with our in-browser editor or via a direct interface to GitHub)”

“With git the more important questions: When do you push? Not as often as possible. I repeatedly regret a push”

“Our git hooks announce when developers push and merges are happening, and who's branches are being deployed.”

“I have been using fugitive.vim for integration with git, I don't know about svn or cvs as I don't use them.”

“I'd been hesitating on Kiln since we use git”

“to transfer information about Git repos. It's been working great”

“A somewhat complete list of tools we use in our startup:”

“In my own startup we're using git to handle our version control as well.”

“I use git locally and on a personal webserver for tons of stuff.”