Tommaso Piazza

Thanks for opening an issue 🎉 Is there a reason why you think carthage should do this as opposed of wrapping carthage commands in a script of your making that...

I see your points, but this in my opinion this is a workflow related choice. Therefore I am reluctant to add this directly in Carthage but, if you want to...

~~credentials are filled with `git credential fill`. This might be a misconfiguration on your side.~~ ~~`[email protected]:Nextdoor/privaterepo.git` would clone with http, not ssh.~~ ~~Please provide a valid example~~ yes, it is...

If you don't want to add another "Cartfile.xxx`, ignoring a scheme could also be specified in the scheme itself as a pre-build action. Carthage would have to parse the scheme...

I believe it can be done by both sides. As an alternative why not just pass scheme ignore names on the command line? like `[--ignore-schems] [SCHEMES]]`

I agree that the `.ignore`file is a better solution. Command line arguments are a nice to have :) Here is how one could do it consumer side by setting ignores...

Cool project! 👍 I'm afraid only `.framework` with Mach-O dynamic or static library are supported

@relikd you can make PR to add support.

run `make clean`

Oh I'm so sorry, I forgot: `make clean && SWIFTPM_BOOTSTRAP=true make` https://github.com/Carthage/Carthage/blob/68abf2d73791720457f5be1aab4b57df86483f88/.travis.yml#L25