Quick question, we've merged a number of commits to the shell-novice lesson
and I've realized that they didn't update the html files.
How should we handle those changes safely? Is a special commit good enough?
--
Gabriel A. Devenyi B.Eng. Ph.D.
Research Computing Associate
Computational Brain
Hi,
We've asked people to submit only the source Markdown for review; topic
maintainers should update and merge HTML when it's ready to bake.
Thanks,
Greg
On 2015-03-18 7:46 AM, Gabriel A. Devenyi wrote:
Quick question, we've merged a number of commits to the shell-novice
lesson and I've
Hi Gabriel,
On Wed, Mar 18, 2015 at 8:48 AM, Greg Wilson
gvwil...@software-carpentry.org wrote:
We've asked people to submit only the source Markdown for review; topic
maintainers should update and merge HTML when it's ready to bake.
On 2015-03-18 7:46 AM, Gabriel A. Devenyi wrote:
Quick
Excellent, I see my co-maintainer spearheaded this and even updated the
repo contributing.md I'm talking about, serves me right for having 300
unread SWC emails...
--
Gabriel A. Devenyi B.Eng. Ph.D.
Research Computing Associate
Computational Brain Anatomy Laboratory
Cerebral Imaging Center
I vote to put the instructions in the README for the default branch
(gh-pages). Note that the current README already has a link to the
contribution guidelines, which contains the instructions about only
committing the Markdown. Let's make the instructions as obvious as possible
for new
On Wed, Mar 18, 2015 at 09:44:59AM -0500, John Blischak wrote:
On Wed, Mar 18, 2015 at 9:38 AM, Karen Cranston wrote:
I vote to put the instructions in the README for the default
branch (gh-pages). Note that the current README already has a link
to the contribution guidelines, which
