Update .spi.yml #206
Merged
Update .spi.yml #206
Conversation
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
Documentation generation fails due to: `error: The workspace named "checkout" does not contain a scheme named "secp256k1_implementation". The "-list" option can be used to find the names of the schemes in the workspace.` This should fix it!
Contributor
Author
|
Alternatively (and this may be what you really want) build the docs on macOS (default) by dropping the platform: version: 1
builder:
configs:
- documentation_targets: [secp256k1, secp256k1_implementation] |
csjones
approved these changes
Jun 28, 2022
Contributor
csjones
left a comment
csjones
left a comment
There was a problem hiding this comment.
Hey @finestructure, thank you for the fix!
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Documentation generation fails due to:
error: The workspace named "checkout" does not contain a scheme named "secp256k1_implementation". The "-list" option can be used to find the names of the schemes in the workspace.This should fix it!