#http pastie org p 1jtkDJYq7PVCZ0nfI6PfCj
1 messages ยท Page 1 of 1 (latest)
It showing me blank rows
https://imgur.com/GzMZCEt
Will it let you git rebase --continue?
[core-ssh config]$ git rebase --continue
You must edit all merge conflicts and then
mark them as resolved using git add
git rebase --skip, since you've deleted it and that's all the commit contained
[core-ssh config]$ git rebase --skip
CONFLICT (modify/delete): www/tmp/snapshot_living_room_sub.jpg deleted in HEAD and modified in a84da5b (config files on 02-03-2023 04:00:00). Version a84da5b (config files on 02-03-2023 04:00:00) of www/tmp/snapshot_living_room_sub.jpg left in tree.
error: could not apply a84da5b... config files on 02-03-2023 04:00:00
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply a84da5b... config files on 02-03-2023 04:00:00
that conflict again
should I abort?
I don't think it'll let you
yeah because we already tried that
Try running the same git rm command again
ok
[core-ssh config]$ git rm www/tmp/snapshot_living_room_sub.jpg
rm 'www/tmp/snapshot_living_room_sub.jpg'
does continue give you the same error
Since it looks like you actually added that folder to your gitignore, you should be able to skip those conflicts, so if you get that again, skip this again
git rebase --continue ?
right
[core-ssh config]$ git rebase --continue
You must edit all merge conflicts and then
mark them as resolved using git add
yeah skip it again
so just git add ?
git rebase --skip
[core-ssh config]$ git rebase --skip
CONFLICT (modify/delete): www/tmp/snapshot_living_room_sub.jpg deleted in HEAD and modified in 1b10a6d (config files on 03-03-2023 04:00:00). Version 1b10a6d (config files on 03-03-2023 04:00:00) of www/tmp/snapshot_living_room_sub.jpg left in tree.
error: could not apply 1b10a6d... config files on 03-03-2023 04:00:00
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 1b10a6d... config files on 03-03-2023 04:00:00
skip again.... for the ones that come up w/ www/tmp, you don't want to preserve any of that anyway
[core-ssh config]$ git rebase --skip
CONFLICT (modify/delete): www/tmp/snapshot_living_room_sub.jpg deleted in HEAD and modified in 6788343 (config files on 04-03-2023 04:00:00). Version 6788343 (config files on 04-03-2023 04:00:00) of www/tmp/snapshot_living_room_sub.jpg left in tree.
error: could not apply 6788343... config files on 04-03-2023 04:00:00
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 6788343... config files on 04-03-2023 04:00:00
same
should I do it again?
yeah
[core-ssh config]$ git rebase --skip
Auto-merging automations.yaml
CONFLICT (modify/delete): www/tmp/snapshot_living_room_sub.jpg deleted in HEAD and modified in 0ae2bfd (config files on 05-03-2023 04:00:00). Version 0ae2bfd (config files on 05-03-2023 04:00:00) of www/tmp/snapshot_living_room_sub.jpg left in tree.
error: could not apply 0ae2bfd... config files on 05-03-2023 04:00:00
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 0ae2bfd... config files on 05-03-2023 04:00:00
how many times should It be?
well you're on march 5th, so a few, it seems
[core-ssh config]$ git rebase --skip
error: The following untracked working tree files would be overwritten by merge:
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4971.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4980.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4995.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f5023.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4971.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4980.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4995.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p5023.jpg
www/upcoming-media-card-images/plex/Recently_Added_TV/f4979.jpg
www/upcoming-media-card-images/plex/Recently_Added_TV/p4979.jpg
Please move or remove them before you merge.
Aborting
hint: Could not execute the todo command
hint:
hint: pick 1276f1402ee9c6e60148cb9cecda1f4892cca8d7 config files on 10-03-2023 04:00:00
hint:
hint: It has been rescheduled; To edit the command before continuing, please
hint: edit the todo list first:
hint:
hint: git rebase --edit-todo
hint: git rebase --continue
Could not apply 1276f14... config files on 10-03-2023 04:00:00
are you wanting to commit those plex images
i don't mind
I just don't want those living room images to be public
(which I added to the gitignore file)
If they're easy enough to regenerate, you could remove them. Otherwise, I think you may need to temporarily move those pictures it references to a separate directory
actually, renaming both of those directories would probably let you abort the rebase
I prefer not to touch anymore and deal with those files
so If i don't mind commit or not those plex images what command should I type in the terminal next?
I do believe in the current state, something has to be done w/ those image files
It won't let you proceed w/o moving or deleting them
Manually?
Right
just the plex/Recently_Added_Movies and plex/Recently_Added_TV
ok
Those are in www/upcoming-media-card-images
through the shell you've got open
(That's what I did with the www/tmp that made all of these problems)..
by git
git rm www/upcoming-media-card-images/plex/Recently_Added_Movies/f4971.jpg
Yeah, if you commit from multiple spots, you'll end up running into conflict. The issue compounded because HA was still making new daily commits and wasn't able to push them
like that?
no, just regular rm
ok
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/f4971.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/f4980.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/f4995.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/f5023.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/p4971.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/p4980.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/p4995.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_Movies/p5023.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_TV/f4979.jpg
[core-ssh config]$ rm www/upcoming-media-card-images/plex/Recently_Added_TV/p4979.jpg
[core-ssh config]$
ok done, what's now
git rebase --continue
[core-ssh config]$ git rebase --continue
You must edit all merge conflicts and then
mark them as resolved using git add
ah, skip again
haha ok
[core-ssh config]$ git rebase --skip
error: The following untracked working tree files would be overwritten by merge:
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4971.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4980.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4995.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f5023.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4971.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4980.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4995.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p5023.jpg
www/upcoming-media-card-images/plex/Recently_Added_TV/f4979.jpg
www/upcoming-media-card-images/plex/Recently_Added_TV/p4979.jpg
Please move or remove them before you merge.
Aborting
hint: Could not execute the todo command
hint:
hint: pick 1276f1402ee9c6e60148cb9cecda1f4892cca8d7 config files on 10-03-2023 04:00:00
hint:
hint: It has been rescheduled; To edit the command before continuing, please
hint: edit the todo list first:
hint:
hint: git rebase --edit-todo
hint: git rebase --continue
Could not apply 1276f14... config files on 10-03-2023 04:00:00
hmmm... did it bring those files back?
how can it do that?
I mean I removed them from my files, not from the git
I added to the gitignore file www/upcoming-media-card-images so it won't upload them anymore
I'm not sure exactly then if you've deleted those files yet it's still coming back w/ them existing
Yeah I deleted them completly by using rm via the terminal
Okay it does coming back by using the trakt integration I have...
Is there a way to ignore them and let the script work then?
I don't believe so, since it's wanting to copy files that will overwrite those
and the only way to "ignore" them is to remove them
It just downloads the artwork of the movies/shows that added last to my plex server
https://imgur.com/0TUopXx
on the Visual basic studio I can pull/push etc the git, should I try one of the options?
https://imgur.com/fNlwAeG
It's a commit from 2 days ago
Does that menu come up when you click continue
after pressing continue I got this error
2023-03-12 16:55:46.181 [info] > git rebase --continue [13ms]
2023-03-12 16:55:46.181 [info] Rebasing (18/21)
error: The following untracked working tree files would be overwritten by merge:
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4971.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4980.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f4995.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/f5023.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4971.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4980.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p4995.jpg
www/upcoming-media-card-images/plex/Recently_Added_Movies/p5023.jpg
www/upcoming-media-card-images/plex/Recently_Added_TV/f4979.jpg
www/upcoming-media-card-images/plex/Recently_Added_TV/p4979.jpg
Please move or remove them before you merge.
Aborting
hint: Could not execute the todo command
hint:
hint: pick 1276f1402ee9c6e60148cb9cecda1f4892cca8d7 config files on 10-03-2023 04:00:00
hint:
hint: It has been rescheduled; To edit the command before continuing, please
hint: edit the todo list first:
hint:
hint: git rebase --edit-todo
hint: git rebase --continue
Could not apply 1276f14... config files on 10-03-2023 04:00:00
and this is on output
If those fiels keep being recreated I don't think you'll have much luck in proceeding
That's the same error that we saw before
so the only solution that I have is to remove the entire repository in my git and create a new one?
I wouldn't say that
I would try
mv www/upcoming-media-card-images/plex/Recently_Added_Movies www/upcoming-media-card-images/plex/Recently_Added_Movies2
mv www/upcoming-media-card-images/plex/Recently_Added_TV www/upcoming-media-card-images/plex/Recently_Added_TV2
git rebase --skip
but the integration automatically brings those photos to the first path
I'd assume after some delay
ok got nothing to lose
let's try
โ /config git:(d4464b9) โ git rebase --skip
Removing www/upcoming-media-card-images/plex/Recently_Added_TV/p4956.jpg
Removing www/upcoming-media-card-images/plex/Recently_Added_TV/f4956.jpg
CONFLICT (modify/delete): www/tmp/snapshot_living_room_sub.jpg deleted in HEAD and modified in a84da5b (config files on 02-03-2023 04:00:00). Version a84da5b (config files on 02-03-2023 04:00:00) of www/tmp/snapshot_living_room_sub.jpg left in tree.
error: could not apply a84da5b... config files on 02-03-2023 04:00:00
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply a84da5b... config files on 02-03-2023 04:00:00
๐ค seems like you're possibly past the other error, but back to Feb in commits
that's a skippable one
so git rebase --skip ?
โ /config git:(d4464b9) โ git rebase --skip
CONFLICT (modify/delete): www/tmp/snapshot_living_room_sub.jpg deleted in HEAD and modified in 53b0ca9 (config files on 12-03-2023 14:35:55). Version 53b0ca9 (config files on 12-03-2023 14:35:55) of www/tmp/snapshot_living_room_sub.jpg left in tree.
Auto-merging automations.yaml
CONFLICT (content): Merge conflict in automations.yaml
error: could not apply 53b0ca9... config files on 12-03-2023 14:35:55
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 53b0ca9... config files on 12-03-2023 14:35:55
โ /config git:(d4464b9) โ git rebase --skip
Successfully rebased and updated refs/heads/master.
git status
So... you should be good to git push .... there's still outstanding image changes, but I'd say probably push first to ensure you're good
don't need to do that yet, you've already added and committed things
just git push
that will sync your rebase to github
/config git:(master) โ git push
Warning: Permanently added 'github.com,140.82.121.3' (ECDSA) to the list of known hosts.
Everything up-to-date
in the repository i don't see a new commit
ok I just ran the automation
it worked.
Thanks dude!
Is there a way now to remove the recently added _ 2 folders?
On your last commands you ran... you skipped 2 commits, but the second one actually had your automations.yaml in it
or just leave them there
I have a feeling that your automations.yaml may have lost some things
why you think so?
Auto-merging automations.yaml
CONFLICT (content): Merge conflict in automations.yaml
error: could not apply 53b0ca9... config files on 12-03-2023 14:35:55
Where do you see that?
yeah looks like it just updated the www folder
instead of all the files (sensors.yaml & automation.yaml)
๐ค
What's git log say
mv www/upcoming-media-card-images/plex/Recently_Added_Movies2/* www/upcoming-media-card-images/plex/Recently_Added_Movies
mv www/upcoming-media-card-images/plex/Recently_Added_TV2/* www/upcoming-media-card-images/plex/Recently_Added_TV
That will copy the files we moved out, back
It'll probably prompt for overwrite
commit 4e8ba7bf2dba40dceac1ea99c858625d4cf6be04 (HEAD -> master, origin/master)
Author: root <root@homeassistant.local.hass.io>
Date: Sun Mar 12 17:11:09 2023 +0200
config files on 12-03-2023 17:11:09
commit d4464b9cd5aa21e091a676628d91d11e0795399d
Author: Ofir-P <79255941+Ofir-P@users.noreply.github.com>
Date: Wed Mar 1 02:20:20 2023 +0200
Delete image directory
commit aad80b779b371ac0b0f478ecc72552ce91b45bef
Author: Ofir-P <79255941+Ofir-P@users.noreply.github.com>
Date: Wed Mar 1 02:19:39 2023 +0200
Delete www/tmp directory
Ofir-P is when I tried to remove directory from the git..
Right, yeah that's just what's in your git repo on Github now
git push -u origin master
wait I will do the two mv commands first
โ /config git:(master) mv www/upcoming-media-card-images/plex/Recently_Added_Movies2/* www/upcoming-media-card-images/plex/Recently_Added_Movies
โ /config git:(master) โ mv www/upcoming-media-card-images/plex/Recently_Added_TV2/* www/upcoming-media-card-images/plex/Recently_Added_TV
โ /config git:(master) โ git push -u origin master
Warning: Permanently added 'github.com,140.82.121.3' (ECDSA) to the list of known hosts.
Branch 'master' set up to track remote branch 'master' from 'origin'.
Everything up-to-date
โ /config git:(master) โ
There you could do git add .
and then your git commit
that will add a new commit w/ those changes
rm www/upcoming-media-card-images/plex/Recently_Added_TV2
rm www/upcoming-media-card-images/plex/Recently_Added_Movies2
So those directories aren't sitting there empty
before the commit, right?
/config git:(master) โ rm www/upcoming-media-card-images/plex/Recently_Added_TV2
rm: cannot remove 'www/upcoming-media-card-images/plex/Recently_Added_TV2': Is a directory
is it like linux that you should do rm -r ?
yeah
ok i will try that
I don't see a new commit in my repository; and will it fix the automation.yaml file too?
You'd have to push to see it show in github
right, but I don't see any change to the sensors.yaml or automation.yaml
and other files that I'm sure they have changed during those 3 weeks
I think you'll have to pull that from the reflog as the skipped commit was the last one in the rebase and the rebase is completed
Is it even possible to do that?
49ebcf6 (HEAD -> master, origin/master) HEAD@{0}: commit: fixed github 12-03-2023 17:21:35
4e8ba7b HEAD@{1}: commit: config files on 12-03-2023 17:11:09
d4464b9 HEAD@{2}: rebase (skip) (finish): returning to refs/heads/master
d4464b9 HEAD@{3}: pull --rebase (start): checkout d4464b9cd5aa21e091a676628d91d11e0795399d
53b0ca9 HEAD@{4}: rebase (abort): updating HEAD
ef94c98 HEAD@{5}: rebase (continue): config files on 10-03-2023 04:00:00
d4464b9 HEAD@{6}: pull --rebase (start): checkout d4464b9cd5aa21e091a676628d91d11e0795399d
53b0ca9 HEAD@{7}: commit: config files on 12-03-2023 14:35:55
c9d2e87 HEAD@{8}: commit: config files on 12-03-2023 04:00:00
c4c5cc1 HEAD@{9}: commit: config files on 11-03-2023 04:00:00
1276f14 HEAD@{10}: commit: config files on 10-03-2023 04:00:00
025c586 HEAD@{11}: commit: config files on 09-03-2023 04:00:00
794bbe0 HEAD@{12}: commit: config files on 08-03-2023 04:00:00
b0b1cf1 HEAD@{13}: commit: config files on 07-03-2023 04:00:00
d4490a3 HEAD@{14}: commit: config files on 06-03-2023 04:00:00
0ae2bfd HEAD@{15}: commit: config files on 05-03-2023 04:00:00
third line?
53b0ca9 is where we started i think
ok with this commit number what should I do to merge it or make it appear in my git?
git reset --hard "HEAD@{7}"
โ /config git:(master) git reset --hard "HEAD@{7}"
HEAD is now at 53b0ca9 config files on 12-03-2023 14:35:55
Well locally nothing changed in my automation.yaml
You sure? Even if you re-open the file
it looks the same, I had the fish alert from the morning
so now should I git add . again?
no, everything is added at this point....
So
Options... you could just force push what you have now, which will nuke the two edits you did by hand
Otherwise.... you could try a merge instead.... but, I don't know if that will run into any issues
You'll have to re-do the 2 edits you did outside of this process
If you're good w/ that, git push --force origin master
The deletion of www/tmp, etc
Oh yeah I don't mind
But I will do that by command and not by going to git manually, right?
(It's typically a very bad idea to do a force push to an actual remote repo, just so you're aware)
Oh
You could do that from the shell after you're done
I just want it to show the updated files of the automation.yaml etc..
I agree, which is why it makes sense to rewrite the history that was pushed
ok so I'm doing the git push and after that will do a command to remove the folder from my git.
๐
rm -r www/tmp ?
if that's what you want to remove, yup. You'll have to re-add to .gitignore as well
ah, looks like it's there already
yeah it's in there
ok, should be good now
I will run the automation to see if automation.yaml gets updated
I see your updates to sensors and automations on your repo
sweet
Thank you man!!!
by the way, is there a way to improve the automation to a diff text on the description of the commit every time it commits or that's too complicated?
because as you can see in my repository it's just saying config files and date, not what has been added/removed
Right, how would you propose it convey that in the comment message though
No idea, that's why I ask the professional guy here
What is your automation doing? or you don't have a github backup automation
Nope, I don't push to github. I just have snapshots and a Google Drive backup
Fair enough
For an automated add/commit, I can't think of a great way beyond like stuffing the list of files changed, but that doesn't seem helpful. You can easily click the commit message to see the diff log
I learned my lesson and won't do it manually anymore, just by commands in the terminal ๐
yeah it will be heavily for the description and too long
Yeah, sorry, I also contributed to it as well. My advice to continue w/ the rebase pull wasn't good and that's where we were stuck for a couple hours
We fixed it, that's what matters!
Protect the ๐
Thank you sir, appreciate that a lot!