Speed up dev build by limiting collections - #1313
Open
adamscott wants to merge 2 commits into
Open
Conversation
Member
|
Ruby 4.0 isn't in either Ubuntu nor Debian repositories (not even Debian testing), so it's kind of a dealbreaker for local builds if it's now required. This would effectively put a hard requirement on building in a container or using mise for contributors. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note
I forked the original repo for my fork because I needed to add missing features with
limit_collectionsand to enable the parallel functionality, even if I didn't include it in this PR. (it messes up with the localization of the website)This PR speeds up the dev build time my limiting the number of collection items processed. It nearly halves the dev build time.
Please note that it will take the latest collection entries, so you'll need to tweak the
_config.development.ymlfile if you need to edit an old blog post (or other hidden content).Warning
I had to update GitHub workflows to use ruby 4.0 to make it work with my fork.