Codespace: Can't commit to a branch, getting "Rebasing..." message. #9
Description
Issue Overview
Codespace: Can't commit to a branch, getting "Rebasing..." message.
I have two branches I have committed to my fork of the CodeSpace repo, and I wanted to commit my changes. I was copying my changes I made in the fork into CodeSpaces editor and committing them. I can't do that now, because of the Rebasing situation. I have two branches I have commits for that are on hold.
Describe your environment
CodeSpace - LinkedIn Learning course "Level Up Java".
"probable acorn"
Steps to Reproduce
- Logged into CodeSpace page from LinkedIn Learning
- Clicked on "probable acorn" linke
- Tried to commit changes
- Stuck with the message "Rebasing in progress", or something similar, where the branch name would normally be shown.
Expected Behavior
I expected it to commit the changes and ask me to do a push.
Current Behavior
Stuck with the message "Rebasing in progress", or something similar, where the branch name would normally be shown.
I tried canceling the rebase, but the Rebase message appeared when I tried to commit again.
Possible Solution
Screenshots / Video
Related Issues
I don't understand how CodeSpaces are billed.
Am I charged for time when I have the Editor up, but I'm not doing anything (like taking a coffee break)?
If I run CodeSpaces remotely (local VSCode) is that billed differently?
If I fork the repo, and use that repo, am I billed for that?
This is probably a GitHub question, but is there a standard way to copy changes made to my fork of the CodeSpaces repo back into the CodeSpaces repo?
If I am not actively using CodeSpaces (logged off GitHub, not running remotely) am I billed for the storage?