Skip to content
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

Update Danger to 6.1.0 and fix issues with running on MacStadium #2945

Merged
merged 7 commits into from
Nov 6, 2019
Merged

Update Danger to 6.1.0 and fix issues with running on MacStadium #2945

merged 7 commits into from
Nov 6, 2019

Conversation

jpsim
Copy link
Collaborator

@jpsim jpsim commented Nov 6, 2019

And validate that running on PRs from forked repos works.

@SwiftLintBot
Copy link

SwiftLintBot commented Nov 6, 2019

12 Messages
📖 Linting Aerial with this PR took 2.31s vs 2.32s on master (0% faster)
📖 Linting Alamofire with this PR took 3.93s vs 3.98s on master (1% faster)
📖 Linting Firefox with this PR took 12.75s vs 12.71s on master (0% slower)
📖 Linting Kickstarter with this PR took 29.52s vs 29.49s on master (0% slower)
📖 Linting Moya with this PR took 2.54s vs 2.63s on master (3% faster)
📖 Linting Nimble with this PR took 2.64s vs 2.67s on master (1% faster)
📖 Linting Quick with this PR took 1.07s vs 1.1s on master (2% faster)
📖 Linting Realm with this PR took 3.96s vs 3.93s on master (0% slower)
📖 Linting SourceKitten with this PR took 1.79s vs 1.77s on master (1% slower)
📖 Linting Sourcery with this PR took 4.58s vs 4.52s on master (1% slower)
📖 Linting Swift with this PR took 21.13s vs 20.99s on master (0% slower)
📖 Linting WordPress with this PR took 33.03s vs 33.05s on master (0% faster)

Generated by 🚫 Danger

@jpsim jpsim changed the title Update Danger to 6.1.0 Update Danger to 6.1.0 and fix issues with running on MacStadium Nov 6, 2019
@jpsim jpsim merged commit da114c3 into realm:master Nov 6, 2019
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