Did you push your changes? All git commands only run against your local repo until a push/pull. If BitBucket already has the commit message you want to change, then you need to `git push --force` because you are overwriting data on the remote repo (this is generally dangerous, if you are working with others I would warn them that you are going to force push)
People like you deserve all the praise in the world. You are here to do one thing and one thing only and it is exactly what you did. No bullshit talking for 30 minutes, straight to the point and easy to follow. Much appreciated.
I believe your editor opens once for each commit message you are creating or rewording. So if you rebase and reword two commits, after saving the interactive rebase step, it'll show you two more editors and you have to write/quit from each. Git supports newlines in a commit messages so putting one in a message doesn't cause any special behavior. Only the first line is visible in some contexts, like `git log --oneline`, but the rest are always there and are visible in a simple `git log` with no extra flags.
@@Blackjac what are the exact steps you're taking? Like `git rebase HEAD~4` and choosing reword? That should reword the given commit message. It will create a _new_ commit to do so, though it doesn't necessarily look like it in the tree (the hash id will change though), but the old one shouldn't stick around. You may have some config setting on that changes the rebase behavior.
@@Blackjac every commit's ID / hash is based on the state of the repo at that time, including commit messages. So essentially all your commits from the revision up to HEAD are rewritten but the code changes remain the same if you're only rewriting a commit message
Run `git push` like you would normally push changes to a remote repo. If the message you want to change is already on your remote repo, you need to `git push -f` but be careful overwriting commits if others are working on the repo too
This was exactly what I needed. In the Git manual online it isn't very clear to me that my editor will pop up twice. You made this very clear and painless. Thank you!
Yes! It does. The first editor lets you choose what you're doing and the second one will appear if you need to edit any previous commit messages, e.g. if you choose "reword" or if you "squash" together a few commits.
Why revert improvements? Wikipedia IS in a permanent state of vandalism and gangs of editors pull out all the stops to keep it that way. If someone knows the difference between deliberate disinformation and vandalism then I am all ears, but if you are going to bore the pants off me with Wikipedia's cherry-picked bundle of "reliable sources" (so-called because they all laud one another and drive home the "correct" narrative), then don't bother. I'll direct you straight to conversations where globalist stooges have jumped up and down in anger over their inability to defend their neo-con values due to the singular bastion for their lunacy "the so-called reliable sources" being impugned by other editors. In short, the neo-cons were not in position to defend their anti-Palestinian and pro-US sentiment because their little fortress was being shaken. Admins are more preoccupied with enforcing policies than writing encyclopaedias (uuurrggghh, banned editor {by our unfounded opinions} made an edit, extinguish extinguish extinguish. Protect the policies; wreck the project).
One way you can fight vandalism is by using recent changes, I have a video but unfortunately it's not uploaded to RU-vid yet reverting edits that say needs review and like today I've reverted like 20 so far
FANTOM X6 Sutradhar this is an example en.wikipedia.org/w/index.php?title=Portal:Judaism/Weekly_Torah_portion/Vaetchanan&diff=969579254&oldid=921591352&diffmode=source
This really helped me so much. Thank you Eric. I never new the command :wq existed and was wondering how on earth I could continue in VIM with the rebase. Much appreciated.
After writing reword infront of the commits, I am unable to get to the last like where we write :wq. I tried clicking on the --INSERT-- line still it won't go. What to do?
Type a colon ":" then the letters "wq" to Write and Quit. These are the controls for the vim text editor, so if you get lost you can look them up online.
Hi, thanks for your video, however I keep running into the same issue which is driving me insane. Happens whether I use terminal in VS Code or the Terminal app. I enter git rebase -i HEAD~2 which opens the screen you see at 01:23. Then the weirdness happens. It won't let me replace pick with reword instantly. At first I'll start typing out reword but nothing happens, then after a couple of seconds it finally lets me do it. I'm assuming you're hitting the ENTER key to go to the next screen right? If I hit ENTER all it does is add a backspace. I basically cannot move past this screen, all I can do is Ctrl + C and then :qa! to get out of it. Any help would be much appreciated. Thanks in advance!
It sounds like you're entering the vim editor which, unfortunately, does not have very intuitive controls. The reason why you start editing after some time is probably because you type the letter "i" eventually which puts you into "Insert" mode and lets you edit. A short summary is to type "i", make your changes, then use ESC to exit Insert mode, then type ":wq" when you want to Write your changes and Quit. You can see me do these steps in the video. I would recommend either learning how to use vim or changing your Terminal's EDITOR environment variable to nano (`export EDITOR=nano` in your bash profile) which is easier to use.
