![]() Branches not appearing in GitKraken – only one of the branches will be detected when they share a name.Most often this appears on Windows machines. For example: Feature/foo and feature/foo may either be detected as the same branch OR a different branch depending on how your operating sytem treats capitalization. This most often occurs when having multiple remote banches nested together, but the capitalization differs. Some branches or files not appearing – Capitalization issue For example: Test-branch > temp-name > test-branch Note: You may need an intermediate name change to get the branch named correctly. You can rename the local branch to match the casing of the upstream remote branch, which will allow you to push the changes. This usually indicates that there is a casing difference between the local branch and the upstream remote branch. When attempting to push a branch, you may see the following Push Failed: Cannot read property 'fullName' of undefined error: If that still does not work, please contact our support team and we can troubleshoot further. Once this is changed you can restart GitKraken Client and attempt to authenticate again. ![]() If that is not working you can also try changing your operating system default browser to be a different browser. If your credentials are correct, you can try signing out of the service in your default browser first, and then attempting the authentication from GitKraken Client again.Ĭlear your browser cache, sign out of the git hosting service, then restart GitKraken Client and try again. First, verify you used the correct credentials then try one of the following potential solutions: ![]() When attempting to connect to one of our integrations, you may see Error 1002, Error 1003, Error 1005 or Error 1007. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |