donnie-jp

Maybe you can add support through the new (I think) https://github.com/MobSF/mobsfscan which doesn't require a server/container - or is that more of an alternative to sast-scan?

I've been experiencing this problem too. My coveralls page shows 0% coverage for a Swift project that is generating coverage using xcov and running CI on travis. https://coveralls.io/github/rakutentech/ios-remote-config https://coveralls.io/builds/25516715 https://travis-ci.com/rakutentech/ios-remote-config/builds/125836479#L2025...

I plan to try https://github.com/nakiostudio/danger-xcov to skip coverage backends entirely and report directly on the PR.

Does the following statement correctly summarize the current behavior? > If a pod exists in multiple source repos and multiple `source`s are specified in the Podfile the CocoaPods dependency resolver...

I also experienced this error, but locally. This issue gave me a hint what was wrong. My remote is not named `origin` and therefore the `git remote show origin -n`...

I see the same issue with a public GitHub repo and a `bundle update` did not resolve it. The github token says it has been used so it seems that...

My issue is resolved by changing my remote name to `origin` - both `local` and `pr` Danger commands work now. https://github.com/danger/danger/issues/870#issuecomment-528154370

This affects our pod https://cocoapods.org/pods/RInAppMessaging too. We released 4.0.0 last week. The podspec was updated correctly but the overview and changelog on the website were not updated. Can this be...

Thanks for responding @orta I don't see anything in the commit log from 2021 that could have caused this so I wonder how long it has been broken. Could the...

> Finally, after 3rd release, the cocoapods page got updated 🎉 (https://cocoapods.org/pods/RInAppMessaging#changelog). > We didn't do anything on our side, so maybe the issue has been fixed. Awesome! Maybe [this...