Closed dzwillia closed 5 years ago
@alwillia Is this fixed? The connection UI has actually been updated since this bug report and now there is no way to actually create a "public" GitHub repo connection.
Yes, this is now fixed, and I verified it using the API. We recently added a connection interface to services that expose a connect() function, which is invoked through the api call, and each service now implements this function.
(You will want to have your developer tools open for these steps)
Works perfectly. The connection status is set to "Connected" and shows a green checkmark.
Now, repeat those steps, omitting step 4:
Fails to connect (the
/connect
call returns with HTTP status code 422). The HTTP response is included below. The connection status is still "Not Connected" and shows a red X (even though the connection can still be queried -- you'll not the file list still shows).