-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Exports.swift #227
Fix Exports.swift #227
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Note: Even though I've bumped the minimum Swift version requirement here, which is normally a semver-minor change, I'm leaving this PR marked no-release-required, on account of 5.6 was already effectively required by the dependency on Vapor, meaning no actual change has taken place aside from silencing the complaints of the 5.4 SwiftPM not knowing about DocC catalogs. |
Codecov Report
|
This officially cleans up the last repo left that still has an uncorrected
Exports.swift
. Cleans up the README and CI workflows too.