Skip to content

Point to correct Reachability repo #175

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

Merged
merged 1 commit into from
Sep 10, 2018
Merged

Point to correct Reachability repo #175

merged 1 commit into from
Sep 10, 2018

Conversation

lucas34
Copy link
Owner

@lucas34 lucas34 commented Sep 10, 2018

Reachability now support SPM. Only on master branch for now.
Will update after the next release.

@lucas-bot
Copy link
Collaborator

2 Warnings
⚠️ The Package.resolved or cartfile.resolved was updated, but not both. Did you forgot to run carthage update or swift package update?
⚠️ The Package.swift was updated, but there were no changes in either the podspec nor Cartfile. Did you forget updating podspec or Cartfile?

Generated by 🚫 Danger

@codecov
Copy link

codecov bot commented Sep 10, 2018

Codecov Report

Merging #175 into master will decrease coverage by 0.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #175      +/-   ##
==========================================
- Coverage   96.73%   96.46%   -0.27%     
==========================================
  Files          25       25              
  Lines        1868     1868              
==========================================
- Hits         1807     1802       -5     
- Misses         61       66       +5
Impacted Files Coverage Δ
Sources/SwiftQueue/Constraint+Network.swift 62.06% <0%> (-17.25%) ⬇️

@lucas34 lucas34 merged commit 2e1d547 into master Sep 10, 2018
@lucas34 lucas34 deleted the SPM_reachability branch September 10, 2018 06:35
This was referenced Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants