Una vez actualizado el email en el área de perfiles, cerre sesión de gitlab y volví a acceder. Por supuesto, aún no había resuelto el problema y lo que realicé fue revisar la configuración y credenciales tanto de GitHub como de GitLab.Įn ese momento me percaté que por accidente, los nombres de dominios de mis cuentas de email estaban mal, había escrito mal el email (Dato muy extraño, ya que antes me había permitido realizar push)
CANNOT READ PROPERTY OF UNDEFINED GITKRAKEN CODE
The issue was resolved by logging out and back inĮl día de hoy 8 de julio 22 tuve el mismo problema, curiosamente tenía abierto Visual Studio Code y me indicaba que tenía un commit para subir.Įs importante mencionar que no estaba logueado dentro de VSC, al intentar realizar PUSH me solicito login y se pudo realizar PUSH. The problem was not in the wrong email of my profile, since when doing it with VSC, the commits I made have the wrong email. On GitKraken, integrations (logins), whether GitLab or GitHub, are independent of the profile. This ultimately allowed me to push from GitKraken. Once the email in the profiles area was updated, I logged out of gitlab and logged back in. Of course, I still hadn't solved the problem and what I did was check the configuration and credentials of both GitHub and GitLab.Īt that moment I realized that by accident, the domain names of my email accounts were wrong, I had written the email wrong (Very strange fact, since before I had been allowed to push) It is important to mention that I was not logged into VSC, when trying to PUSH I was asked to login and PUSH could be performed. Curiously, I had Visual Studio Code open and it indicated that I had a commit to upload. Today, July 8, 22, I had the same problem. A more meaningful message that describes the problem, or at least some of the common causes such as this, would be nice.
After that I was able to push my branch successfully.ĭefinitely a pretty bad user experience. I decided that cleaning up all the old branches was a good thing to do anyway, so I deleted them all. I noticed that the remote repository had a lot of stale branches that had never been cleaned up, and the thought occurred to me that perhaps the cause could be a name clash. To my great surprise, I received the same error on the fresh repository with a new branch. I tried a few different things to no avail, even including deleting the local repository and cloning again. When I tried to push, I received this error. I had created a new branch with a fairly generic name. In this case, the solution is to either choose a different (unique) name for the local branch being pushed, or delete the remote branch with the same name. I just experienced this error as well, and to add one more potential cause to the list, in my case it was because:Ī remote branch already exists with the same name as the branch being pushed. The error is certainly not very useful, as evidenced by the various causes captured in the answers here.
0 kommentar(er)
