-
Notifications
You must be signed in to change notification settings - Fork 47
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
Cant connect to Gitlab to deploy my app #1450
Comments
@mzabalza can we hop on a call with you. |
yes of course |
@Sepudev @mzabalza can you please share your account ID via a DM on our community discord server? My username is swaminator. |
@swaminator I left you a message on discord dm! |
@Sepudev i responded. Please send us your account ID. |
@swaminator I am having the same issue. |
@emily-malone @griffins-planera can you please share your account ID via a DM on our community discord server? My username is |
hey @Jay2113 @swaminator, thank you for your help. |
@Jay2113 @swaminator I tried to contact by discord and got no answer, in our team we have not been able to connect and we have a little stuck this issue, no solution for the moment? |
@emily-malone @griffins-planera can you please share your account ID via a DM on our community discord server? My username is |
Hi everyone, We're going to track all further discussions and updates in ticket #1490. Please post any new information or questions there. Closing this issue as a duplicate. Thank you! |
Environment information
Description
Since the new Aws Amplify UI I am not able to connect aws amplify to my gitlab account.
All our team is experiencing the same issue not only with one aws account but with several.
This are the exact steps to reproduce the bug:
6 . Pop up closes but reopens immediately and even if I keep clicking in Authorize it keeps reopening.
7 sometimes the pop up dissappears but I dont see any branch option:
In another aws account I did the connection one month ago so that connection is correctly linked but when I try to make a connection to a new branch the error is the same.
No matter the aws account, the gitlab user, this issue is always present.
Our time relies on aws amplify to deliver different projects to different clients and to be unable to even connect it to gitlab where all our codebase is hosted its a big issue for us.
The text was updated successfully, but these errors were encountered: