Closed d4h0 closed 10 years ago
I'm surprised that didn't work, as your steps make sense.
What do you get when you run git status
? I'd try git reset --hard
, git fetch upstream
, and git merge upstream/master
.
git status said there are many files that are newly added or changed. Your suggestion didn't work.
I've deleted and re-installed the app and now updating seems to work.
I don't have much experience with Git and I've probably done something wrong.
Anyway, thanks for your help!
Another related question that I have is do I have to re-run bundle before "git push heroku master" when I update Huginn?
Hey @bolus, while you don't have to re-run bundle
before you git push heroku master
doing so won't hurt anything. Any new/updated dependencies will get installed locally and if nothing has changed in the Gemfile it will execute rather quickly. However, it would be a good idea to run bundle
again should you rerun bin/setup_heroku
.
Now this is just because I'm curious: Are you by chance running Windows locally? I feel like it is possible that some configuration or program you've used may have changed the line endings in some files and that might have caused those merge conflicts. Just a hunch.
Try the solution below, it worked for me using windows.
https://github.com/cantino/huginn/commit/85fb86b1cb459d723e8462f9c1cf50036440d787
Thanks @zperrault. No, I don't use Windows. I'm using Mac OS X
@signallhill, thanks but reinstalling Huginn fixed the problem already.
So, oddly, I got this too and fixed it with git remote add public https://github.com/cantino/huginn.git && git fetch public && git merge public/master -X theirs
, but this will lose any code changes you've made in your fork and so should only be used right after a fresh launch of the Heroku button. Does anyone know why this is happening with Heroku? It's like git has no idea about the history.
/cc @knu @dsander
Looks like the repository created for the app by Heroku consists of one commit which imports a snapshot of the original master on GitHub, so it does not have a fast-forward relationship with the original repository.
We could probably make setup_heroku
run git remote add origin https://github.com/cantino/huginn.git && git reset --hard origin/master && git push --force --set-upstream heroku master
in the very first run.
Checking if there is no commit made by user could be confirmed with [ $(git log --oneline | wc -l) -eq 1 ]
.
@knu, I think that's a good idea. This is a confusing experience right now. Would you mind trying that? If you don't have time, I'll give it a go.
@cantino Please review the PR above!
Hi,
How do I update Huginn if I have used the Heroku button to deploy it?
Can someone please add this information to https://github.com/cantino/huginn/wiki/Run-Huginn-for-free-on-Heroku ?
I've tried:
git remote add upstream https://github.com/cantino/huginn.git git fetch upstream git checkout master && git merge upstream/master
After that I was planning to run
git push heroku master
but the command before failed with the output at the end of this message.
Best regards, Daniel