#git (149 links)
I mean they can but this is actually a fairly balanced take on why it's even more useful to know about right now.
- How Core Git Developers Configure Git blog.gitbutler.com
- Conventional Comments conventionalcomments.org
Comments that are easy to grok and grep
- Sapling: Source control that’s user-friendly and scalable engineering.fb.com
We’ve spent the past 10 years building Sapling, a scalable, user-friendly source control system, and today we’re open-sourcing the Sapling client. You can now try its various features using Sapling’s built-in Git support to clone any of your existing repositories. This is the first step in a longer process of making the entire Sapling system available to the world.
- Monorepo Explained monorepo.tools
With GitOps, all changes to infrastructure and application deployment are versioned, immutable, auditable, and reversible, offering guarantees that cannot be made with a cultural shift or by one team taking over the responsibilities of another.
This is magic.
- social.coop · GitLab git.coop
Tools and structures from social.coop, "a coop-run corner of the fediverse"
- Highlights from Git 2.38 | The GitHub Blog github.blog
Rebase dependent branches with `--update-refs`
- Guide To GitOps weave.works
- [Common Issue] Troubleshooting your Netlify Large Media Configuration - Support / Common Issues - Netlify Community community.netlify.com
¯\_(ツ)_/¯
- Sublime Merge - Git Client, done Sublime sublimemerge.com
- Git - git-clean Documentation git-scm.com
Remove untracked files from the working tree
- naholyr/github-todos github.com
<blockquote>A git hook to convert your TODOs into Github issues.</blockquote>
- How to use private Github repo as npm dependency stackoverflow.com
- Force push with care robots.thoughtbot.com
Prefer the flag --force-with-lease over --force to the git push command.
- Six cool features of the Git 2.x series - Atlassian Developers developer.atlassian.com
Workspaces look useful.
- How to undo (almost) anything with Git github.com
- Automating a Git Rebase Workflow | bazaarvoice: engineering blog.developer.bazaarvoice.com
- The Humble Squerge! | Personal Website of Rémy Bach remy.bach.me.uk
<blockquote>Let’s talk about force pushing in Git. We’ll cover when you should do it, when you shouldn’t, and how to do it safely.</blockquote>
- How to write the perfect pull request github.com
- On committing well slideshare.net
<blockquote> What should git commits look like? How should comments work? A brief review of some good practices, complete with examples where I've made mistakes myself.</blockquote>
- How GitHub uses GitHub to document GitHub github.com
<blockquote>I basically now have both the simplest and most sophisticated multi-language ebook production and distribution setup on the planet.</blockquote>
Beautiful, if you like this sort of thing.
- pre-commit by Yelp pre-commit.com
Introduction At Yelp we rely heavily on pre-commit hooks to find and fix common issues before changes are submitted for code review. We run our hooks before…
- git - Push to gist returning strange error - Stack Overflow stackoverflow.com
Change the remote.
- A few of my Git tricks, tips and workflows · The Nuclear Squid nuclearsquid.com
Including "Disable “how to stage/unstage/add” hints given by git status"
- “Merge pull request” Considered Harmful | Spreedly Blog blog.spreedly.com
I love Github – I think it’s made contributing to open source 1000% more approachable and enjoyable. But I’ve found the open source maintainer workflow that…
- Draft. Write Better. draftin.com
<blockquote>Easy version control and collaboration to improve your writing.</blockquote>
<blockquote>Write better with a simple markdown editor, version control and easy collaboration tools.</blockquote>
- git-up - fetch and rebase all locally-tracked remote branches aanandprasad.com
git pull has two problems:
* It merges upstream changes by default, when it's really more polite to rebase over them, unless your collaborators enjoy a commit graph that looks like bedhead. * It only updates the branch you're currently on, which means git push will shout at you for being behind on branches you don't particularly care about right now.
- Checking out Pull Requests locally · GitHub Help help.github.com
<blockquote> Let's say someone's made a pull request from their fork into your repository. Here's how you can check out her changes on your machine and verify that everything is a-okay.</blockquote>
- How to Create a New and Empty Branch in Git bitflop.com
<blockquote>$ git checkout --orphan NEWBRANCH</blockquote>
- a simple git branching model gist.github.com
- Darian Moody : Heroku deployment without the app being at the repo root (in a subfolder) coderwall.com
<blockquote>git subtree push --prefix appfolder heroku master</blockquote>
- Subtree merging and you nuclearsquid.com
The clearest explanation I've found for git's subtree merge.
- git ready » easily fetching upstream changes gitready.com
- Changing History with Git | Flippin' Awesome flippinawesome.org
- Commit Often, Perfect Later, Publish Once—Git Best Practices sethrobertson.github.io
- Working with subtree merge · GitHub Help help.github.com