Can't access new GitHub organization for Automated builds

removing third-party app restriction worked for me.

https://github.com/organizations/YOUR_ORGANIZATION/settings/oauth_application_policy

1 Like

Itā€™s 2019 and this issue from 2015 is still unresolved. None of the recommended solutions here work either- Iā€™ve unlinked and relinked my account multiple times, made sure the ā€œthird party app restrictionā€ was enabled for docker hub, and I still canā€™t get the organization to show up in the new repository page.

3 Likes

Iā€™m having the same problem, too. None of the methods mentioned above worked for me. :frowning:

Thank you kizbitz for help us, your response fix this problem.

I am trying to create a ā€˜service userā€™ as per the documentation, but Iā€™m really having trouble with this point. Iā€™ve followed these directions:

  1. made sure the SU was a public member of the org and has write access to at least 1 repository
  2. unlinked the github account at DOCKERHUB/orgs//settings/linked-accounts and DOCKERHUB/settings/linked-accounts for my SU (though sometimes clicking the plug symbol does not appear to change anything).
  3. revoked access to docker registry on GITHUB/settings/applications
  4. re-link application through both the organization and my profile

After trying this multiple times combined with logging out and logging in, I still am unable to access my organizationā€™s repository. @kitzbitz, is there any solution?

Edit: the solution was to make the ā€˜service userā€™ an OWNER of the repository and not just have write or maintenance permissions.

To be fair, this is present in the documentation:

This service account should have access to any repositories to be built, and must have administrative access to the source code repositories so it can manage deploy keys. If needed, you can limit this account to only a specific set of repositories required for a specific build.

It might be that I am alone in my misinterpretation, but there are a couple of reasons why I did not see ownership as a requirement:

This transition was bad for my dyslexia: "... so it can manage deploy keys. If needed, you can..." I had mentally switched the full stop and comma so that it read "... so it can manage deploy keys, if needed. You can..."

If you read the two sentences and flip the comma and full stop like I did, it suggests that the administrative access is only needed if you explicitly want deploy keys (to where? I though maybe back to GitHub).

I think the documentation could be improved a bit to avoid this mistake:

This service account should must have access to any DockerHub repositories to be built, and must have administrative access to the source code repositories so it can manage deploy keys. If needed yYou can also optionally limit this account to only a specific set of repositories required for a specific build.

This clarifies what is required and what is optional.

Same problem - I am unable to see all of the organizations I am a member of, even those where I am a public member. I also notice that for some organizations I am unable to see all of the public repositories in that organization.

Further, looking at the dev console, I see a lot of redā€¦ I submitted a ticket to Support.