-
Notifications
You must be signed in to change notification settings - Fork 1
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
Gemfile specified 2.4.0 #2
Comments
Hmmmm, This is what I see.
|
RUBY VERSION |
Well that... is strange. Dumb question: could you verify you're on See: https://github.com/mdwheele/classroom/blob/feature/support-ghe/Gemfile.lock#L520 |
That said, I found the "bug" and have a workaround I need to send to that PR. The API endpoint is returning I'm going to implement a workaround so we can get further and at the same time reach out to our representative with GitHub and see what the deal is. The feature is documented in the enterprise API documentation as "there") |
That was it. I had checked out a whole new copy for this
|
Good news on the bug hunt! Thanks for working at it! |
No problem at all. I have a feeling the constant gap between GitHub and GitHub Enterprise regarding the API is going to become a bigger and bigger blocker. Hopefully, I can get a patch into Octokit for this, but if I were them, I don't think I would take something like this without a better "compat shim" for the library which will take more time. |
Any update on things? I'm getting ready to ping instructors doing a pilot with us, and I was hoping to give them a chance to try out Classroom via GHE. I guess we're waiting on upstream to look at the GHE API response problem? |
Yeah, I'm waiting on GitHub to get back to me. I was able to reproduce the issue outside of Classroom or my PR. The only other thing I know to try is to attempt to detect the bugged output and, at that point, sift through all current invitations to find the |
./classroom build
succeeds and I can go into./classroom shell
but I get this error:The text was updated successfully, but these errors were encountered: