Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy fail due to Jekyll include syntax - How to FIX? #35

Open
rnag opened this issue Jan 31, 2024 · 0 comments
Open

Deploy fail due to Jekyll include syntax - How to FIX? #35

rnag opened this issue Jan 31, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@rnag
Copy link

rnag commented Jan 31, 2024

Hi,

Thanks for creating this lib @sinedied . I have QQ, when I have blog post usually with these contents

{% include <site>.html %}

Now to be honest i'm really no clue how is this action is parsing that above. Like if it reads the html file directly and parses as markdown. The problem actually is even within that <site>.html file, I have some kramdown syntax in there, which is not compatible with markdown:

Blah blah... lolol
{: .notice--info}

Just an example of course. Now I'm not 100% sure how this action is parsing it. But in either case it's failing it with a nondescriptive error. I had to do trail-and-error to figure out that the cause is because of {% include ... %} syntax.

Q

Ideally, my Q here is as follow:

  • How do the publish-devto know to exclude when it encounter such a syntax like:
    {% include ... %}
    E.g. does it try to evaluate it and read html file, and that's why its failing, it encounter kramdown? or does it fail just because it sees include syntax?
  • How can I work around this. Ideally I will like to skip that line that starting with {% include ... %} altogether. How can I achieve this. I tried modifying it in yml directly, but deploy still fails I guess because git status --porcelain shows error, since file is modified since i had to remove that offending line.
  • If above else not possible, I like to pass markdown contents instead of markdown file. Is that possible currently? Will it solve git status issue where it's trying to check if no dirty changes checked out before it commits to dev.to or update on GH?

Appreciate help or clarification on this. Thanks

@sinedied sinedied added the enhancement New feature or request label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants