You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Couldn't add Xcode project at path file:///Users/mxbot/myproject/myproject.xcworkspace, error: Cannot find the Checkout/Blueprint file and failed to parse repository metadata directly. Please create an issue on GitHub with anonymized information about your repository. (Error Disallowed checkout type, the project must be checked out over one of the supported schemes: SSH).
Although the repo was clone using SSH I followed the workaround steps creating the blueprint file but I still get the same error.
Is it possible to get more detail about what is producing the error?
first of all, great issue report! That's all I need to be helpful here.
I can see from your blueprint that your repo URL is git@github.mycompany.com:myorg/myproject.git, which implies you're using GitHub Enterprise, instead of github.com, correct?
If so, technically Buildasaur doesn't yet support Github Enterprise servers, but there are a couple of people working on it (and have their forks), see this issue with links: #99. There's even a WIP pull request: #251.
Hope this helps. As I don't have an Enterprise server myself, I can't get the support in myself, so I'm relying on contributors. It might be worth to try to chat to them directly.
Yup looks related to the github enterprise instance. Our setup is not standard, I will check the issues as PRs you referenced and see if I can be of some help
As we don't technically yet support GitHub Enterprise yet, I'll close this. If you're using a fork of Buildasuar, it's probably best to open a ticket in the fork's issues section and later try to ask them to PR the improved version into main Buildasaur. Unfortunately I cannot help with forked code as I don't know what's been changed.
I got the following error adding a repo:
Although the repo was clone using SSH I followed the workaround steps creating the blueprint file but I still get the same error.
Is it possible to get more detail about what is producing the error?
The blueprint file added looks like (anonymised):
Thanks for your work!
The text was updated successfully, but these errors were encountered: