docs: clarify where .jekyll-metadata comes from#8646
Merged
jekyllbot merged 2 commits intojekyll:masterfrom May 14, 2021
Merged
docs: clarify where .jekyll-metadata comes from#8646jekyllbot merged 2 commits intojekyll:masterfrom
jekyllbot merged 2 commits intojekyll:masterfrom
Conversation
0a5d822 to
c203450
Compare
kmk3
added a commit
to kmk3/jekyll
that referenced
this pull request
Apr 20, 2021
It's currently missing from the Directory Structure page: https://jekyllrb.com/docs/structure/ Relates to jekyll#8646
kmk3
added a commit
to kmk3/jekyll
that referenced
this pull request
Apr 20, 2021
It's currently missing from the Directory Structure page: https://jekyllrb.com/docs/structure/ Kind of relates to jekyll#8646.
This was referenced Apr 20, 2021
In its overview section[1], link to the incremental regeneration page[2] and show how to create the file. That page is the only one that mentions both the file by name and also how/when it gets generated (e.g.: with the `-I` flag). [1] https://jekyllrb.com/docs/structure/ [2] https://jekyllrb.com/docs/configuration/incremental-regeneration/
0c5b425 to
cffce35
Compare
kmk3
added a commit
to kmk3/editorconfig.github.com
that referenced
this pull request
Apr 20, 2021
* .jekyll-cache/: created when running e.g: `jekyll serve` [1][2] * .jekyll-metadata: created when running e.g.: `jekyll serve -I` [1][3] [1] https://jekyllrb.com/docs/structure/ [2] jekyll/jekyll#8648 [3] jekyll/jekyll#8646
xuhdev
pushed a commit
to editorconfig/editorconfig.github.com
that referenced
this pull request
Apr 20, 2021
* .jekyll-cache/: created when running e.g: `jekyll serve` [1][2] * .jekyll-metadata: created when running e.g.: `jekyll serve -I` [1][3] [1] https://jekyllrb.com/docs/structure/ [2] jekyll/jekyll#8648 [3] jekyll/jekyll#8646
DirtyF
approved these changes
May 14, 2021
Member
|
@jekyll: merge +docs |
jekyllbot
added a commit
that referenced
this pull request
May 14, 2021
github-actions bot
pushed a commit
that referenced
this pull request
May 14, 2021
Kelvin M. Klann: docs: clarify where .jekyll-metadata comes from (#8646) Merge pull request 8646
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a 🔦 documentation change.
Summary
In its overview section, link to the incremental regeneration page and
show how to create the file. That page is the only one that mentions
both the file by name and also how/when it gets generated (e.g.: with
the
-Iflag):https://jekyllrb.com/docs/configuration/incremental-regeneration/
Context
I wanted to see if this file is ever generated (or if it was deprecated or
something) and how to do so before adding it to a .gitignore file, as I only
use
jekyll serveanyway.It took me a long while to find out how to generate it (I had to clone the repo
and grep around).