You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your hard work and this beautiful tool. I'd like to have dedicated configuration while where jilu, or rather tera, can read the customization from. With that, we can simply redirect the jilu output into a file. Putting them into the changelog file itself causes inconvenience like, even if I can use sponge, some reason jilu still uses default configuration.
The text was updated successfully, but these errors were encountered:
@kondanta while moving the config to a separate file would fix the behaviour you describe, the behaviour is a bug in parsing the config out of the Markdown comment, not a general problem with the approach.
Hi!
Thank you for your hard work and this beautiful tool. I'd like to have dedicated configuration while where jilu, or rather tera, can read the customization from. With that, we can simply redirect the jilu output into a file. Putting them into the changelog file itself causes inconvenience like, even if I can use sponge, some reason jilu still uses default configuration.
The text was updated successfully, but these errors were encountered: