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

Add dedicated configuration file #15

Open
kondanta opened this issue Jun 14, 2020 · 1 comment
Open

Add dedicated configuration file #15

kondanta opened this issue Jun 14, 2020 · 1 comment

Comments

@kondanta
Copy link

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.

@jcgruenhage
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants