Hi,
Right now, the `lesson-template` repository has two branches:
* `core` holds the CSS files, page layouts, and checking script that
will be copied into every lesson.
* `gh-pages` holds that, plus the example files showing how to lay out
lessons.
The idea is that authors add `core` as a remote to their lesson so that
they can pull in changes to CSS and the like *without* re-adding example
files that they probably deleted early on in the construction of their
own lesson. The problem is that several people have stumbled over
submitting stuff to `lesson-template` because of the two branches.
The alternative is to have a separate repository called `lesson-core`
that holds those things likely to be updated periodically. When people
create a lesson, they can either copy in `lesson-template` (to get the
example files) and then delete the stuff they don't need, or start
directly with `lesson-core`. Either way, `lesson-core` is what they'll
add as a remote repository to get updates.
I think these approaches are equally usable in the hands of Git
experts. I'd therefore be grateful for feedback from non-experts as to
which they'd prefer. If you have a preference, please add your thoughts
to https://github.com/swcarpentry/lesson-template/issues/118. (If
you're unable to comment on that ticket, please let me know and I'll
give you permissions.)
Thanks,
Greg
p.s. please respond on the ticket rather than to this message so that we
can keep traffic on this list manageable.
--
Dr. Greg Wilson | [email protected]
Software Carpentry | http://software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
