![]() This increases the time I spend on a task by a certain margin. Given that I’m not sure how communication works between yours and GitKraken’s team - or if there is any communication for that matter, I’ve posted this lengthy feedback, maybe it will help someone else or prompt you guys to look into the issue.įor my current client this bug is a serious nuisance because it forces me to do the above steps sometimes even multiple times a day, in addition to reinstalling all dependencies with each new cloning. If I work on a feature branch that points to a different commit other than develop does for either of these submodules, upon trying to switch to develop and pull the latest changes I am continuously prompted to re-authorize GitKraken in Gitlab. I am able to consistently reproduce the issue by working with a repository that uses a number of git submodules. gitkraken folder in Roaming (Windows user here) and cloning the repository again - contacted GitKraken support for that. Meanwhile I managed to correct the issue by deleting the. After reauthorizing again, it says that I am connected.ĭear your for your follow-up on this thread, I really appreciate it. I logged out of gitlab and back in, and after exiting and reopening GitKraken, it continues to say I am not connected. Retry without OAuth gives me an error saying “ Push Failed: failed to write chunk header: The server returned an invalid or unrecognized response” However, it keeps giving me this pop up no matter how many times I re-authorize. I checked inside GitKraken, and I am authenticated. Refresh Token takes me to a GitKraken page in the browser, which indicated that I was authenticated and the system would work. Would you like to refresh your OAuth credentials or try again without OAuth?” and presents the following three options: However, when I went to push, it gave me a pop up saying “ Your OAuth token for ‘Gitlab’ is invalid. This is something I do commonly without error. You will also see how to use the magic of GitKraken to revert a Git commit with the. Select the key you wish GitKraken Client to use when signing your commits and annotated tags. Signing Key: This dropdown list will contain all of your local keys. Launch GitKraken Client and navigate to Preferences GPG Preferences. I am trying to push changes to my branch using the GitKraken GUI. Follow the steps below: Online First log in and go to your profile. Once you have GPG installed on your machine, you will need to configure GitKraken to use GPG.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |