diff options
| author | Jason R. Coombs <jaraco@jaraco.com> | 2019-02-06 09:58:28 -0500 |
|---|---|---|
| committer | Jason R. Coombs <jaraco@jaraco.com> | 2019-02-06 09:58:28 -0500 |
| commit | 8186f76e906f80d678e895f6627afefee5617888 (patch) | |
| tree | 05d02153656f12324ae316850e849e484c457773 | |
| parent | 12eed1326e1bc26ce256e7b3f8cd8d3a5beab2d5 (diff) | |
| download | pytest-runner-8186f76e906f80d678e895f6627afefee5617888.tar.gz | |
Amend skeleton documentation to expand on the value of the approach.
| -rw-r--r-- | skeleton.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/skeleton.md b/skeleton.md index 0e0c0ef..09485cc 100644 --- a/skeleton.md +++ b/skeleton.md @@ -10,6 +10,8 @@ It's intended to be used by a new or existing project to adopt these practices a The primary advantage to using an SCM for maintaining these techniques is that those tools help facilitate the merge between the template and its adopting projects. +Another advantage to using an SCM-managed approach is that tools like GitHub recognize that a change in the skeleton is the _same change_ across all projects that merge with that skeleton. Without the ancestry, with a traditional copy/paste approach, a [commit like this](https://github.com/jaraco/skeleton/commit/12eed1326e1bc26ce256e7b3f8cd8d3a5beab2d5) would produce notifications in the upstream project issue for each and every application, but because it's centralized, GitHub provides just the one notification when the change is added to the skeleton. + # Usage ## new projects |