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

Add Carthage shield to README #39

Merged
merged 2 commits into from Jun 25, 2015
Merged

Conversation

cojoj
Copy link
Contributor

@cojoj cojoj commented Jun 25, 2015

Hmm, I guess @czechboy0 assigned this silently to me in #30 and thanks to a teamwork (kudos @esttorhe) we're officially supporting Carthage which has been tested and works pretty nice.

Here's the README update with beautiful Carthage shield and updated Sources section.


I don't know if you guys will like it but I've created a table covering features which compares XcodeServerSDK with official API endpoint/possibilities.

czechboy0 pushed a commit that referenced this pull request Jun 25, 2015
Add Carthage shield to README
@czechboy0 czechboy0 merged commit 77b65df into buildasaurs:swift-2 Jun 25, 2015
@czechboy0
Copy link
Member

Awesome, @cojoj, thanks!

@czechboy0
Copy link
Member

BTW all of those endpoints that Apple officially supports and we don't we can easily add. Just add a method in XcodeServer and possibly a new endpoint in XcodeServerEndpoints. It would be nice to support all the Apple endpoints plus some. Do you want to create an issue for this? Should be an easy one for anyone with 20mins on their hands. Thanks!

@cojoj
Copy link
Contributor Author

cojoj commented Jun 25, 2015

Yeah, I'll create issue for this with a nice bullet list 😉

@czechboy0
Copy link
Member

Ok, sounds good. I also made a couple of fixes, so base the checklist on the new readme version: e694947

@cojoj cojoj deleted the carthage-readme branch June 25, 2015 07:55
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.

None yet

2 participants