{"action":"opened","issue":{"url":"https://api.github.com/repos/Carthage/Carthage/issues/366","labels_url":"https://api.github.com/repos/Carthage/Carthage/issues/366/labels{/name}","comments_url":"https://api.github.com/repos/Carthage/Carthage/issues/366/comments","events_url":"https://api.github.com/repos/Carthage/Carthage/issues/366/events","html_url":"https://github.com/Carthage/Carthage/issues/366","id":59342164,"number":366,"title":"--dry-run","user":{"login":"robrix","id":59671,"avatar_url":"https://avatars.githubusercontent.com/u/59671?v=3","gravatar_id":"","url":"https://api.github.com/users/robrix","html_url":"https://github.com/robrix","followers_url":"https://api.github.com/users/robrix/followers","following_url":"https://api.github.com/users/robrix/following{/other_user}","gists_url":"https://api.github.com/users/robrix/gists{/gist_id}","starred_url":"https://api.github.com/users/robrix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robrix/subscriptions","organizations_url":"https://api.github.com/users/robrix/orgs","repos_url":"https://api.github.com/users/robrix/repos","events_url":"https://api.github.com/users/robrix/events{/privacy}","received_events_url":"https://api.github.com/users/robrix/received_events","type":"User","site_admin":true},"labels":[{"url":"https://api.github.com/repos/Carthage/Carthage/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-28T13:41:37Z","updated_at":"2015-02-28T13:41:37Z","closed_at":null,"body":"Sometimes it would be nice to be able to do a dry run: resolve dependencies & solve constraints, even download stuff, but don’t move anything into `Carthage/Checkouts` or build or anything. Basically, everything that won’t write within `$SRCROOT`. (It’d be great if a dry run could also check for the presence of shared schemes, too.)\r\n\r\nI think this would be helpful for folks who don’t know Carthage yet to build confidence with it (both confidence in their use of it and confidence in it itself), as well as being a quicker way to test complex configs for projects with transitive (inter)dependencies.\r\n\r\nCarthage is nondestructive, so I wouldn’t block 1.0 on this or anything."}}