I connected to my git project successfully in github - I can push, pull, and commit changes. I am, however, unable to use the "manage branches" function even though I am connected to the project. I took a screenshot of my log because I can't attach txt files - it says there's a null value for username and password which is a bit odd.
Thanks for your assistance.
3 Answers, 1 is accepted
I am sorry to hear you have encountered such trouble and will be happy to assist you further.
However, there are some additional details on your end to be able to better understand what might be going wrong. What I understood so far is that you are unable to manage the Git repo branches when trying to do this in Test Studio. Upon reviewing the log file, you noticed the error for the missing username and password.
Though, I am not sure what is the behavior or appearance of the logged error when you attempt to manage the branches - can you please elaborate on that? Is there an error to popup when trying to do this in Test Studio or the branch button is disabled at all?
You mentioned that push, pull and commit command can be successfully performed. Do you perform these in Test Studio as well? What is listed in the Output panel for the performed actions? Are there any errors? How did you open the project - did you open the local repo or connected again to the Git and then selected the project?
If you open the Git Connect wizard, do you see password and username listed there? Have you recently updated your credential for the Git project? Have you changed these in Test Studio as well? Do you have two-factor authentication enabled for the repository in question?
If you open Git Bash command prompt and try to operate with the repository from there, will you face any troubles or errors?
Please, excuse me for the multiple questions listed, however there are important detail I am still not familiar with. So, I am looking forward to hearing back from you once you have the time to gather the above details. Thanks in advance for your cooperation.
P.S. On a side note, let me please, mention that you can attach archived files (*.zip and *.rar) and this is how you can pack the log file and send it whenever necessary.
Regards,
Elena Tsvetkova
Progress Telerik
Sorry, I get the logged error only when I right click my project or test files > Git Source Control > Manage Branches. There's no Error popup in test studio - the entry I linked is the only in the logs. No pop ups or anything when I try to manage branches.
Yes, I am preforming everything in test studio, and my push, pull, and commit actions appear in the output panel. There aren't any errors when I push, pull, or commit. If I check my git repo, I can see that they were all successful. I created a completely new project to test this out - I created a blank repo first, then pushed and commited my new project to it after I connected.
I can't open the git connect wizard anymore - it is greyed out in my nav bar. I only input my credentials once. I do not have two-factor authentication enabled.
I have not tried git bash command - I am not the most familiar with git.
Thank you for the additional details and please, excuse me for the delayed response.
I was trying to reproduce the same error on my end, but to no avail. The described misbehavior is quite strange and as I am not able to explore it on my end, I will need some further assistance on your end.
First thing to give a try to is to disconnect the project from source control:
1. Please open the project
2. Click the right mouse button on the project and select the option to 'Remove the Source Control Binding'.
3. Then Connect again and re-enter the username and password.
What will be the outcome of the above? Will you be able to manage the branches now?
You mentioned that you used the Project explorer options from the context menu - do you observe the same behavior if you use the Branches icon in the upper ribbon?
And the last proposal I have on the case will be if you can create a brand new github user and try with it? I hope this will not be an issue for you, however if you have any concerns, please let me know.
If none of the above does not change anything, we can schedule a meeting to explore the issue on your end. So, I am looking forward to hearing back from you and then we will decide how to proceed.
P.S. Please, be informed that I will be out of the office until next Thursday and this will be the first day available to meet in case this will be necessary. Thank you in advance for your understanding.
Regards,
Elena Tsvetkova
Progress Telerik