adding instructions for contentprovider extension #824
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
betatim
reviewed
Dec 5, 2019
|
|
||
| This is a living document talking about the architecture of repo2docker | ||
| from various perspectives. | ||
|
|
||
| ```eval_rst | ||
| .. _buildpacks: | ||
| ``` |
There was a problem hiding this comment.
What does this do? Is this a way to smuggle RST into an otherwise MD file?
|
Thanks for getting our documentation into shape. Feels like a "new years resolution to get stuff in order" spirit and it isn't even 2020 yet! |
markmo
pushed a commit
to markmo/repo2docker
that referenced
this pull request
Jan 22, 2021
adding instructions for contentprovider extension
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.
This does two things:
This is related to jupyterhub/binderhub#1017. Eventually the two docs should probably reference one another, as adding a new RepoProvider in BinderHub is often paired with adding a new ContentProvider in repo2docker. This also makes me wonder why it's called "RepoProvider" in one and "ContentProvider" in another...