-
Notifications
You must be signed in to change notification settings - Fork 21
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
Refactor package.resovled check #645
Refactor package.resovled check #645
Conversation
… of the Package.resolved files
f3597e2
to
a92e6bf
Compare
ca49e78
to
1df52eb
Compare
…/swiftpm/Package.resolved
1df52eb
to
76f0f75
Compare
|
App Name | ||
Build Number | 2070 | |
Version | 1.0 | |
Bundle ID | com.automattic.gravatar-sdk-demo-uikit.prototype-build | |
Commit | 89a92ce | |
App Center Build | Gravatar SDK Demo - UIKit #576 |
This branch currently contains:
So the Dangerfile check should fail. And it does: Note that only one error is returned. Danger appears to be deduplicating errors. I have confirmed locally that each function call causes the warning (by commenting out the other function call). |
I just implemented the
And it fails the build, too. Let's keep the Dangerfile check. The output is easier to find. |
…and both of the Package.resolved files" This reverts commit a92e6bf.
Placing this in Milestone 6, since it shouldn't block the release. I'm still targeting the release branch, though, in case we can merge it before we release. |
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.
Closes #642
Description
This unwinds #643 and approaches the challenge differently, using existing plugins from Danger and Buildkite.
Testing Steps
TEST: Update...
commit. [Check out: 9ea7e8b]Package.swift
manually (without updating thePackage.resolved
(Ideally, this change would remove a plugin, in order to reproduce the events that led to this change, but I think any change is sufficient)