Allow deployment from Github organization repositories
Once authorized, the list of repositories only includes its own repositories, not the repositories from the organization(s) that the user belongs to and has access.
The current workaround is to create a fork of the organization repository, but this limits the ability to continuously deploy on changes.
This works today as previous comments explain.
David Ebbo commented
Setting up continuous deployment from org repos has always been supported. The key is that you need to have admin permission on the repo, so that web hooks can be set up. So generally, the rule of thumb is that if you can manually set up a Web Hook on GitHub, continuous deployment will just work.
Byron Tardif commented
This is fixed, here is the blog post with details:
Richard Turner commented
Ben & Team - do you have an update on this request? I've just moved several repo's to our new company org, but cannot setup CI via Azure :(
Johan Eliasson commented
I agree. This is a absolute must, since the members of a GitHub Project/organization isn't the owner of the repository. I followed Florin's recommendation, and that worked fine for now.
Simon Needham commented
Well, I just ended up here too. Ended up using the an Owner account workaround mentioned by Florin.
Actually I was able to do this, as long as I am in the Owners group for the organization. You need to make sure that the "Third Party Access" section of the org settings shows "Windows Azure" as approved.
Andrew Turner commented
Stephen Oakman commented
We would like this ability as well. Just spent 30 minutes googling to find an answer before finding this top. ****!