StackBlitz sends an empty/duplicate commit to linked GitHub repo

[jordanhailey]

Description of Bug

After setting up a new create-react-app project and connecting to a GitHub repo, I've noticed that two commits are sent each time I commit -> push from StackBlitz.

• The first commit contains all file changes and whatever commit message I have chosen to send.
• The second commit is "empty" in that is has no file changes associated with it, but it does have the default message of N file(s) modified.

Steps to Reproduce

1. Create a project and link to a GitHub Repository
2. Edit any file(s).
3. Click "Commit" and either enter a custom commit message or use the automated message.
4. Navigate to the linked repository on GitHub and see commit history.

Expected Behavior

Only one commit is sent with the file changes, the message either being a custom commit message or the default if no message is specified.

Screenshots/Screencast

• See example of this issue in my repository also pictured below for posterity (in case I delete the repo), I placed a pink outline around the empty/duplicate commits.
  

Additional Context/Questions

• Application url link

[Lonli-Lokli]

@jordanhailey are you still able to push your code from stackblitz to github? I do not even see push button, connect is broken too

[jordanhailey]

Hey @Lonli-Lokli

I was able to test this again just now, I can still commit (and it still pushes two commits to my repo)

Not sure what might be causing issues on your end, do you see a "Commit" button near the top of your IDE? If not, perhaps you haven't linked your GitHub account?

[Lonli-Lokli]

@jordanhailey I think it's because you have your token in place. I had to logout and after that I see this when trying to connect the repo - failing request and constantly loading page.

But login itselff was successfull, I can see all projects. I just cant do anything with github

https://pasteboard.co/K5ZUyLt.png

[jordanhailey]

Ah shame.. I'm sure the team is moving at rapid pace and may have that bug resolved soon. 🤞🏽

[aymeric-guittard]

Hello! 😄

I am having the exact same issue. I managed to "fix" it by developping on an other branch, and squashing the commits when merging. I'd still very much like this issue fixed 😅

[mikitachyzhyk]

Same issue, please fix.

[kc0tlh]

This issue is now resolved in our new VS Code editor! Additional details in Github issue #2473