It seems like there is a crucial and huge but using the GitHub and no one from Google is addressing this.
This has happened to many users, and yet - silence.
P.S
The fix for this bug is kind of easy and fast, which won’t demand any real efforts..!
1 Like
Hi @Dis-cord
Thank you for bringing this to our attention.
I completely understand frustration. To help us investigate further, could you please provide more details to reproduce the issue, along with any error messages you are encountering?
Thanks again for your patience.
1 Like
מעולה. הוספת הקישור לשרשור המדווח ופרט נוסף על כשל ה"מחובר אך מנותק" יעצימו את הדיווח.
להלן הניסוח המלא והסופי באנגלית, כולל כל הפרטים והעדכונים שביקשת:
Thank you for your reply.
The essential problem is that the failure occurs randomly and unpredictably. To help your team identify the root cause, I am providing a detailed technical sequence of events leading up to the failure.
Detailed Sequence of Events Leading to Failure
-
Project Creation: I created a new project, clicked “SAVE TO GITHUB” (STG), created a new repository via the resulting window, and successfully pushed the initial version.
-
Continuous Work: For a period of days or even weeks, I worked on the project. After every set of changes, I clicked STG, confirmed the change list, and successfully pushed the updates to the existing repository.
-
Random Failure: At an unspecified, random time, clicking STG does not bring up the commit and push window. Instead, the initial “Create New Repository” window reappears.
-
Consequence: Even when I attempt to provide the name of the existing repository, the system displays an error and requires me to create a new repository, which prevents me from updating my current, active project.
Important Note on Clones: I frequently clone projects (e.g., “COPY OF…”) and continue working on the new clone. I suspect this issue might be related to changing the names of these cloned projects, though I am not certain as this has only occurred twice under those specific conditions.
Workarounds Attempted and Critical Side Effects
I tried the following steps, which only worked for some projects and failed for others:
- Revoke and Re-Authorize: I revoked the Google Studio permissions from GitHub, clicked STG again (which prompted me for re-authorization), and in some cases, after a refresh, I was able to update the existing project.
Critical Issues with this Workaround:
-
Loss of Chat History: This “fix” completely wipes out my entire chat history with the system. Consequently, if the pushed update fails in the external environment, I cannot revert to a previous working version because the chat history, which serves as the version history, is gone. (I strongly urge the implementation of a feature to save chat/version history.)
-
Prolonged Blocking: The last time I revoked permissions, the system took many hours before allowing me to log in again. During this time, I was completely blocked from working on the project.
-
Inconsistent Connection Status: On one occasion, after revoking and re-authorizing permissions, I was visually connected to GitHub (as seen in the window), but the system still identified me as ‘not logged in’, preventing any push operations.
-
Ultimate Failure: Even after successfully logging back in and re-synchronizing with GitHub, clicking STG still required me to open a new project – which I was ultimately forced to do.
Proposed Immediate Improvements and Streamlining
I believe these two improvements would significantly streamline the workflow and address the secondary issues caused by the main failure:
-
Manual Disconnect/Connect Button: Provide a dedicated “Log In” and “Log Out” option for GitHub (separate from the STG button). This would allow me to manually control the connection status and resolve broken links proactively.
-
Save to Existing Project Capability: Allow me to save files to an existing GitHub repository instead of forcing me to create a new one whenever synchronization is lost.
Thank you for your attention to this matter. I am hopeful for a quick system update regarding this issue.
P.S. (1): You can also see more users experienced this in this thread: https://discuss.ai.google.dev/t/github-login-issue-with-google-ai-studio/104757
P.S. (2): I would also like to suggest a quality-of-life improvement: Currently, there is no option to report a bug while inside the project page. I am forced to leave the project environment and navigate back to the main dashboard to create a report. Allowing users to report issues directly from within the project would significantly improve the feedback process.
-
Mine from project X
-
From user @PineappleBingo
3. Mine from project Y
4. The existence of the project on Github and the Model asks me yet to open a new one.
Just now it happened once again on the new version I just opened after the last time…
This happened right after I did a copy of this version while the old version was open on another tab (The old one which I need it’s history’s chat).
is there anyway to retrieve lost version?
I made an effort and wrote such a detailed comment, and you just ignore and won’t respond or update?
This is not very respectful, especially when those bugs still exist.
So there are changes in the system since this post was created, but this bug wasn’t fix - and yet I get it again on another project that I already fiinshed, and wanted to add more deatures as an upgrade, but will need to open a new repistory just for this, which is just noonsense!
WE DESPERTLY NEED AN OPTION TO ASSIGN OUR PROJECT TO AN EXISTS REPISTORY!
