I am unable to export changes to the repo #170011
Replies: 3 comments 1 reply
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
so you mean, you had 120 hours of Codespaces without committing ? that's quite an unusual Dev practice, small commits are always preferred and may even be required by companies that at the end of the day you commit things that you need to commit Codespaces has the habit of stopping after period of inactivity like 15 minutes, in this case they are still saved but in the case of exhaustion, then yes, your work is lost but you had the chance before this even happens so my advice is about preventing it to happen as good Dev practice, are incremental commits, that no matter what happen, it's always saved on GitHub |
Beta Was this translation helpful? Give feedback.
-
|
I ofc didn't have 120 hrs of uncommited work. I usually commit after every change. But this time, I was working on a major feature for which I didn't commit so basically 2-3 hrs od work was uncommitted that's it. Since I got no response from github support I just redid the work. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
I have exhausted my 120 hrs of codespace, and it randomly stopped working with it having my uncommited code on it, now when I click the "export uncommitted changes to a branch" button, it just fails.
Beta Was this translation helpful? Give feedback.
All reactions