Add Swift package index yml file #900
Merged
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
kimdv
requested review from
ahoppen,
allevato,
bnbarham and
shawnhyam
as code owners
|
@swift-ci please test |
|
Thank you, Kim. Could you address the failures? Looks like adding |
kimdv
force-pushed
the
kimdv/add-swift-package-index
branch
2 times, most recently
from
c91e101 to
263d371
Compare
kimdv
force-pushed
the
kimdv/add-swift-package-index
branch
from
263d371 to
3e7534a
Compare
kimdv
force-pushed
the
kimdv/add-swift-package-index
branch
from
3e7534a to
dba874b
Compare
|
@ahoppen I think it is all fixed now |
|
@ahoppen I see it failed: https://swiftpackageindex.com/swiftlang/swift-format/builds If I compare with swift-syntax is don't pass the same parameters. |
|
This seems to be an issue with swiftpackageindex.com: SwiftPackageIndex/SwiftPackageIndex-Server#3558 |
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 PR will the spi.yml file, so Swift Package Index can build the documentation.
I was thinking of only adding this, and then in follow up PR's add more markdown files, so like documentation for rules and configuration can be found easily.