2017-07-05 20:27:24 +02:00
|
|
|
## Checklist
|
|
|
|
|
|
2022-01-29 20:17:23 +01:00
|
|
|
- [ ] I have search the [issue list](https://github.com/danog/gojekyll/issues) for my issue.
|
2017-07-10 01:20:26 +02:00
|
|
|
- [ ] I have verified the behavior with `jekyll`.
|
|
|
|
|
- [ ] I tried hard to create a reproducible test case.
|
2017-07-05 17:18:00 +02:00
|
|
|
|
2017-07-07 15:36:10 +02:00
|
|
|
## System information
|
2017-07-05 17:18:00 +02:00
|
|
|
|
2017-07-06 16:43:43 +02:00
|
|
|
Liquid version: `gojekyll --version`
|
2017-07-07 15:36:10 +02:00
|
|
|
|
2017-07-05 17:18:00 +02:00
|
|
|
Commit hash: (if version = `develop`)
|
|
|
|
|
|
2017-07-07 15:36:10 +02:00
|
|
|
## Expected behavior
|
2017-07-05 17:18:00 +02:00
|
|
|
|
|
|
|
|
|
2017-07-07 15:36:10 +02:00
|
|
|
## Actual behavior
|
2017-07-05 17:18:00 +02:00
|
|
|
|
|
|
|
|
|
2017-07-07 15:36:10 +02:00
|
|
|
## Steps to reproduce the behavior
|
2017-07-05 17:18:00 +02:00
|
|
|
|
2017-07-05 20:27:24 +02:00
|
|
|
Provide the first of these that is practical:
|
2017-07-05 17:18:00 +02:00
|
|
|
|
2017-07-05 20:27:24 +02:00
|
|
|
1. A Go test case function.
|
2017-07-05 17:18:00 +02:00
|
|
|
2. A single file that demonstrates the problem. Put this in a directory and run `gojekyll -s path/to/directory`, and we'll see the issue.
|
|
|
|
|
3. A two-file site that demonstrates the problem. Put the `_config.yml` and the other document in a directory, etc.
|
|
|
|
|
4. A link to a repo that demonstrates the problem.
|
|
|
|
|
5. Something is wrong but I don't have time or knowledge to fully isolate it. Here's the best description I can provide.
|
2017-07-05 20:27:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## Possible Solution
|
