Skip to content

Conversation

@JJ
Copy link
Collaborator

@JJ JJ commented May 11, 2018

Explanation of everything in the latest commit. Gist of it is: you might need to add new files generated by Hugo by hand, push is not automatic, but at least a commit with a standard message ("these files have been changed", I know, probably not very good) is generated and saves you some hassle.

JJ added 7 commits May 11, 2018 14:28
This addresses codeisscience#20. It would have to be way more complicated if new
Hugo files had to be checked out. Maybe it's not a big deal, but if
that's the case it will print a message so that they can be added
manually.

I'm kind of wary of adding a push here... You neendn't push after each
commit, and it's probably reasonable to just leave the commits there
for editing if needed.

Also: commits could be squashed... Left as future work and if
absolutely necessary.
@yochannah yochannah self-requested a review May 11, 2018 13:13
Copy link
Collaborator

@yochannah yochannah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JJ Thanks for this! I agree that we shouldn't push after thinking about this - I would be furious if something pushed on my behalf. How do I test? When I checked out I mage a change to a content md and a test commit but I couldn't see any changes. Am I doing it right? :)

@JJ
Copy link
Collaborator Author

JJ commented May 11, 2018 via email

@yochannah yochannah merged commit af575a4 into codeisscience:master May 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants