#git (176 links)
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.
- How to write the perfect pull request github.com
- On committing well slideshare.net
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.
- How GitHub uses GitHub to document GitHub github.com
I basically now have both the simplest and most sophisticated multi-language ebook production and distribution setup on the planet.
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"
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…
Easy version control and collaboration to improve your writing.
Write better with a simple markdown editor, version control and easy collaboration tools.
- 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
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.
- 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
git subtree push --prefix appfolder heroku master
- Subtree merging and you nuclearsquid.com
The clearest explanation I've found for git's subtree merge.
- mislav/hub github.com
A command-line tool that makes git easier to use with GitHub.
- 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
- Smart branching with SourceTree and Git-flow – SourceTree by Atlassian blog.sourcetreeapp.com
SourceTree supports git-flow.
- git ready » rolling back changes with revert gitready.com
Another helpful option is the -n or --no-commit flag. This will simply leave the reverted changes in your working directory and not automatically commit them.
Lifesaver.
If you are not using Git, you will find yourself facing an increasing number of competitors who are, and a decreasing pool of candidates who are willing to tolerate the alternatives.
"A free, open source solution for creating github repositories from the commandline avoid the usual copy and paste." Needs lots of work.
- A Baseline for Front-End Developers - Adventures in JavaScript Development rmurphey.com · Archived on
I think we’re seeing the emphasis shift from valuing trivia to valuing tools. There’s a new set of baseline skills required in order to be successful as a front-end developer, and developers who don’t meet this baseline are going to start feeling more and more left behind as those who are sharing their knowledge start to assume that certain things go without saying.
- Epic Pull Requests epicpullrequests.tumblr.com
- Why aren't you using git-flow? - Jeff Kreeftmeijer jeffkreeftmeijer.com
Parses your readme's markdown into a clean and simple documentation website. Made especially for your gh-pages branch, all you need is a single index.html file that includes the DocumentUp script.