Change liquid converter order

[jyruzicka]

• Liquid tags are now parsed after converters are run on files.
• Liquid tags are encoded as HTML comments (sample: <!--LIQUID-a4ef62-2-->) during conversion, using the new LiquidEncoder class.
• {% include %} liquid tag will now run included files through converters if any match their extension
• Docs have been updated to explicitly mention order of parsing for files with YAML front-matter, and to mention that included files are converted if their extension matches.

[mattr-]

568900c, a3826dd, and 73bdd7b all have commit messages that are too long. Please see http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html for how to write proper git commit messages.

[jyruzicka]

@mattr Cheers for the feedback - first time contributing to someone else's repo rather than just keeping my own in check, so expect some newb mistakes.

What's the preferred method of fixing git commit messages?

[mattr-]

I'm actually not sure. I've never had to do that before.

[ixti]

You can't change commit messages on remote. Instead you can git rebase -i
on local branch and open a new pull request. See:

• https://help.github.com/articles/interactive-rebase
• http://gitready.com/intermediate/2009/01/31/intro-to-rebase.html
  On 29 Mar 2013 05:01, "Jan-Yves Ruzicka" notifications@github.com wrote:

@mattr https://github.com/mattr Cheers for the feedback - first time
contributing to someone else's repo rather than just keeping my own in
check, so expect some newb mistakes.

What's the preferred method of fixing git commit messages?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/895#issuecomment-15628074
.

[jyruzicka]

@ixti Thanks! git rebase navigated, I'll re-submit the pull request.