This repository has been archived by the owner on Mar 10, 2023. It is now read-only.
Extract brisk core pipeline stages into a package #218
Conversation
This file contains 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
dpisani-atl
force-pushed
the
extract-brisk-pipeline-package
branch
2 times, most recently
from
7b7d579 to
b97ba11
Compare
Add changeset Move default pages back into the gatsby generator package
dpisani-atl
force-pushed
the
extract-brisk-pipeline-package
branch
from
b97ba11 to
26c1285
Compare
🦋 Changeset is good to goLatest commit: a6830da We got this. Not sure what this means? Click here to learn what changesets are. |
Noviny
approved these changes
Jan 23, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I'd like to use brisk's inner logic for docs extraction in a separate project. To this end, I've created a new package to expose some of brisk's pipeline stages for consumption.