On Mon, Mar 09, 2015 at 10:17:55PM +0000, Matt Davis wrote: > Not all of those workshop pages link to associated lessons, but I > think we should make that a standard practice.
And even if they did link to the associated lesson, we're currently missing a way to show the rendered content of that lesson (e.g. swcarpentry/git-novice) as it was taught. I'd recommend we cut versioned releases of our lessons, so folks can link to (for example) https://swcarpentry.github.io/git-novice/v1.2.3/. That's also useful for making sure the lesson doesn't change under your feet the day before you teach from it ;). > Especially after having merged everything into a single workshop > repo? Hmm, if folks are *merging* the lessons into their workshop repository. I'm not sure how to track how folks have been using the v5.3 lessons, but I was imaging them linking (via HTML/Markdown) instead of merging (via Git). I don't see notes about either approach here [1]. > How is this going to affect the size of our lesson repos? It won't effect their size (so long as you don't merge the PRs), unless you're running something like: [remote "github"] url = git://github.com/swcarpentry/git-novice.git pushurl = ssh://[email protected]/swcarpentry/git-novice.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* where the +refs/pull/*/head:… refspec will bring in local copies of all the PRs. Even then, it's just increasing your local repo size by downloading the PR branches. Cheers, Trevor [1]: https://github.com/swcarpentry/workshop-template -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
