Git Remote Repository Disappears
Posted: Fri Sep 06, 2019 7:27 am
My team authors in Flare (2018 r2 currently; working on pulling the trigger to move to 2019) and uses git (BitBucket) for source control (integrated Flare source control UI).
Various members of my writing team are having issues with the specified remote repository "disappearing" on them, so that when they go to pull from or push to the repository, the dropdown in the dialog window that usually contains the repository is empty instead of containing the repository we defined upon binding. Their projects are still bound, but whenever attempting the pull or push actions, the remote repository is no longer available for selection. As far as I can tell, no specific action or event occurred prior to the issue manifesting that may have caused it.
I have had team members experiencing this issue re-define the remote repository URL and alias directly in this dialog window, but this often results in differing error messages ("Remote already contains another project. Please pull/push from/to an empty remote." OR "Cannot set empty URL.") and a failure to pull/push.
I am at a bit of a loss for how to solve this issue; it happens often enough where it has sort of crippled our source control utilization. Has another else experienced this issue or possibly have some insights into what may be happening? Any help is appreciated, as always; this community is awesome. Thank you!
Various members of my writing team are having issues with the specified remote repository "disappearing" on them, so that when they go to pull from or push to the repository, the dropdown in the dialog window that usually contains the repository is empty instead of containing the repository we defined upon binding. Their projects are still bound, but whenever attempting the pull or push actions, the remote repository is no longer available for selection. As far as I can tell, no specific action or event occurred prior to the issue manifesting that may have caused it.
I have had team members experiencing this issue re-define the remote repository URL and alias directly in this dialog window, but this often results in differing error messages ("Remote already contains another project. Please pull/push from/to an empty remote." OR "Cannot set empty URL.") and a failure to pull/push.
I am at a bit of a loss for how to solve this issue; it happens often enough where it has sort of crippled our source control utilization. Has another else experienced this issue or possibly have some insights into what may be happening? Any help is appreciated, as always; this community is awesome. Thank you!