- Image Diff Example
- GitHub Blog: Introduce Image Diff | PSD support
- GitHub Blog: Introducing Maps | Diffing
- CFPB Pages site
- NIST 800-63-3 Policy | Repo
- Federal Source Code Policy Public Commenting
- Code.gov collaboration
- US Government APIs
- HealthCare.gov StyleGuide Repo | StyleGuide
- GSA Federalist
- 18F Micro-purchase | [Repo](https://github.com/18F/micropurchase/
- GSA Agile BPA | Repo Actual TO have their own repos
- GSA Open Source Policy | Also talks about best practices for open sourcing
- atom/atom
- How to write the perfect pull request
- Writing good commit messages
- 5 useful tip for a good commit message
- The art of the commit
A few links to various sites and discussions of branching strategies I share with users who have questions. In general, I suggest branches be created for all bug fixes and new features, and if it is a particularly large change, you can have a "branch of branches."
- Worth reading: The original work on Git branching strategies (I now find this outdated and overly complicated): nvie.com
- High level overview of GitHub Flow: readthedocs.io
- Good article using a development branch and GitHub Flow: medium.com
- A discussion of branching considerations: creativebloq.com