GitLiveApp / GitLive

GitLive Docs
82 stars 24 forks source link

Cannot select issue to work one #35

Closed khatibtamal closed 3 years ago

khatibtamal commented 3 years ago

When I select an issue to work on. I get the following error.

gitlive_error

I dont use master branch, but main.

Thanks

michaelprichardson commented 3 years ago

Hi @khatibtamal, thanks for letting us know about this. Could you please let us know what version of the GitLive plugin you are currently using?

khatibtamal commented 3 years ago

hello @michaelprichardson I believe it is 10.0.5

git_live_version

michaelprichardson commented 3 years ago

Hi @khatibtamal,

Apologies for the delay but I believe it should be fixed now. Your default branch should be set to main now.

Please let me know if you are still getting the error

khatibtamal commented 3 years ago

Hi @khatibtamal,

Apologies for the delay but I believe it should be fixed now. Your default branch should be set to main now.

Please let me know if you are still getting the error

hello @michaelprichardson yes it has worked now. thanks!

malicean commented 3 years ago

Was this fixed applied to other issue trackers? I seem to be getting an identical error with the same cause, but I use GitHub instead of GitLab. I'm currently on 11.1.0 via JetBrains Rider 2020.3.4.

michaelprichardson commented 3 years ago

Hi @ash-hat

Thanks for letting us know! Just want to find out a bit more info so I can help fix this. Is the message the same as above? Is it trying to checkout master and your repositories default branch is main? Did the default branch name for the repository change recently?

malicean commented 3 years ago

Yes, same error: screenshot of error I also had the same branch names: master (old) and main (new).

The branch did change recently, about 36 hours ago. I noticed it after deleting my stale local branches, including master, a little past 24h after the name change.

michaelprichardson commented 3 years ago

@ash-hat if you manually check out the main branch in the repository with the changed branch names, it will pull the updated branch name and you should be able to select an issue. Let me know if there are any issues.

Apologies, it seems like the change took longer than expected to propagate.