Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to push to github #958

Closed
lmame opened this issue May 2, 2019 · 14 comments
Closed

Failed to push to github #958

lmame opened this issue May 2, 2019 · 14 comments

Comments

@lmame
Copy link

lmame commented May 2, 2019

I am at ngConf 2019 and was working on a workshop.
I took the trainer stackblitz, forked it and used stackblitz to create a repo on my github.
It went ok.
Locally on my laptop I cloned the repo and added the slides (20MB+?).
On stackblitz I pulled the modification (no error message).
I worked on the workshop and tried to commit.
It failed with an error message (not simple enough for fast forward, use force).

Then now the stackblitz project cannot even load anymore:
https://stackblitz.com/edit/ngconf2019-bz-angular-ngrx

Import error, can't find files:
/src/main.ts
/src/index.html
/src/styles.css
/src/polyfills.ts
/src/app/app.module.ts
/src/app/app.routing.ts
/src/app/app.component.ts
/src/app/app.component.css
/src/app/app.component.html
/src/app/hello.component.ts
/src/app/banana/banana.component.ts
/src/app/banana/banana.component.css
/src/app/banana/banana.component.html

@AmmonK
Copy link

AmmonK commented May 8, 2019

I received the same error with a JavaScript project. I hard-reloaded the page and was able to make my commits after that. I'm not sure if Git has a different state for when the project is first connected vs when it is reloaded. This might not work for you since it's a different project type but at least in this scenario it worked.

@joselvelez
Copy link

I am getting the same issue on a tutorial that I am playing around with. Using Angular.

@dimitrihartt
Copy link

What is the workaround for that, please?

@willi84
Copy link

willi84 commented Jun 4, 2019

@lmame I see this when I click your link:

image

@krishnadevz
Copy link

You can download that folder on your local computer and then push to the github ok that is also way or you can fork bt i am not able to fork that ok i hope this help

@menaka-siri
Copy link

menaka-siri commented Sep 10, 2019

@lmame
It seems that StackBlitz fails to push the commits to Github when you try to click on the commit button after few hours, I think. I couldn't track the exact time period.
But when I push commits with short time intervals (within minutes), the code changes have been successfully pushed to the repo.

@seiyria
Copy link

seiyria commented Sep 25, 2019

One solution that worked for me was to make a new branch and merge them via PR on github. I would like to just be able to force push always though, as I have no intention of editing this project outside of stackblitz.

@massimocoletti
Copy link

is it possible to perform commit with additional parameters?

@ashishkummar
Copy link

Please update when this issue got fixed from stackblitz

@jeserkin
Copy link

Okay. Found a dirty workaround.

  1. Chose different branch from branch list (e.g. New branch)
  2. Stash changes into new branch (it will only close base branch and switch to it)
  3. Now commit existing changes into new branch
  4. On Github create PR on new branch
  5. Merge PR into base branch
  6. Delete tmp branch
  7. In stackblitz switch to base branch and pull changes
  8. Profit!!!??? Not really.

@yuwash
Copy link

yuwash commented Feb 20, 2021

Yes, @jeserkin’s method (stash) is the only thing that worked for me so far. Neither pulling nor creating a new branch helped (in a Javascript project).

Bonus: if you want to customize the commit message, you can pull it in the console, git commit --amend it and then merge it to the base branch locally and push it (continue with step 6).

@jeserkin
Copy link

jeserkin commented Mar 2, 2021

I still feel like it could be solved more elegantly.

@kc0tlh
Copy link
Collaborator

kc0tlh commented Aug 23, 2023

This issue is now resolved! Full writeup in Github issue #2473

@kc0tlh kc0tlh closed this as completed Aug 23, 2023
@lmame
Copy link
Author

lmame commented Sep 13, 2023

Thanks @kc0tlh :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests