marcgrep CLI demo
5:59
4 ай бұрын
Spotting PayPal Phishing Emails
6:00
My #1Lib1Ref Edit (2016)
8:58
8 жыл бұрын
(netrunner) Haarpsichord vs Gabe
8:15
(netrunner) MaxX vs. Making News
16:04
Chrome Extensions | ACRL Tech Connect
15:54
Sass & CSS Preprocessors | CCA WAG
1:00:01
Rewriting Commit Messages in Git
2:35
Vandalism on Wikipedia
2:41
11 жыл бұрын
Moving & Deleting Files in a Git Repo
3:01
Fix a Broken Link on Wikipedia
5:57
11 жыл бұрын
Eric Explains URLs
3:09
11 жыл бұрын
Automating Gmail Signatures
3:29
12 жыл бұрын
Speech Input for Web Forms
3:28
12 жыл бұрын
Remove Twitter Promotions
0:39
12 жыл бұрын
Пікірлер
@mdreaj55
@mdreaj55 9 ай бұрын
Extension Name??
@phette23
@phette23 9 ай бұрын
It was named "Remove Twitter Promotions" but it no longer works and I've removed it from the web store
@timothytimm7040
@timothytimm7040 Жыл бұрын
this is awesome thanks for the video it helped me a lot👌
@kingslayer5403
@kingslayer5403 Жыл бұрын
I used the ammend command but it did not reflect in the BitBucket.
@phette23
@phette23 Жыл бұрын
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)
@TarasAnichyn
@TarasAnichyn Жыл бұрын
Thanks)
@SamScott_jr
@SamScott_jr Жыл бұрын
Thank you
@diwakardayal954
@diwakardayal954 Жыл бұрын
Wow 8 year ago xD how are u doing nice video btw
@Klonoa1488
@Klonoa1488 Жыл бұрын
get a life losers
@pickupmidland3523
@pickupmidland3523 2 жыл бұрын
Cry moar
@Omar-id9hv
@Omar-id9hv 2 жыл бұрын
🌹 𝘱𝘳𝘰𝘮𝘰𝘴𝘮
@vertexforger
@vertexforger 2 жыл бұрын
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.
@jonathanharris2326
@jonathanharris2326 2 жыл бұрын
What would you do on the final screen if you were rewording multiple commits? Do you go to a new line and type the message?
@phette23
@phette23 2 жыл бұрын
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.
@danalex2991
@danalex2991 2 жыл бұрын
Thanks for the tip !
@fatememirjalili
@fatememirjalili 2 жыл бұрын
Thank you so much!
@flueepwrien6587
@flueepwrien6587 2 жыл бұрын
why does it create a new commit when i try this :(
@phette23
@phette23 2 жыл бұрын
Try what part? `git commit --amend` or `git rebase`?
@Blackjac
@Blackjac Жыл бұрын
@@phette23 For some reason it does the same for me. whenver i try to rename a past commit it makes a new commit of the one im trying to reword.
@phette23
@phette23 Жыл бұрын
@@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
@Blackjac Жыл бұрын
@@phette23 ahhh i see, so I'd have to drop the old commits if i want to delete a commit that contains i.e (typos etc)
@phette23
@phette23 Жыл бұрын
@@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
@AverageGuy513
@AverageGuy513 2 жыл бұрын
How do this changed log msg gets pushed to the server ?
@phette23
@phette23 2 жыл бұрын
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
@Henry_Nunez
@Henry_Nunez 2 жыл бұрын
Windows o Linux ? 🤔
@Henry_Nunez
@Henry_Nunez 2 жыл бұрын
👍
@Kiki-hf4yf
@Kiki-hf4yf 3 жыл бұрын
"Billy, your answer was incorrect, Math isn't your mom." "But Mrs. Susan, Wikipedia said it is, they don't lie right?"
@TasniMarwane
@TasniMarwane 3 жыл бұрын
Thank you, sir, thank you very much.
@stephanie_ong
@stephanie_ong 3 жыл бұрын
Awesome video! This was a great refresher for me who has not used rename in a while.
@hyfydistro
@hyfydistro 3 жыл бұрын
What if it's like 50 commits long ago?
@BukuiZhao
@BukuiZhao 3 жыл бұрын
Anyway do you have huggle? I have and that is what I use to revert vandalism
@BukuiZhao
@BukuiZhao 3 жыл бұрын
Btw today I have reverted like 15 vandalism so far (account is User3749)
@BukuiZhao
@BukuiZhao 3 жыл бұрын
Actually if you try to edit that locked page its a semi so you can edit it but not everyone
@erichepperlewp
@erichepperlewp 3 жыл бұрын
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!
@MommaWolf1967
@MommaWolf1967 3 жыл бұрын
Wikipedia is not based on Truth or fact
@AyrtonPeralta
@AyrtonPeralta 3 жыл бұрын
really useful, thanks!
@millieandcupcake
@millieandcupcake 3 жыл бұрын
Hi how do i rewrite 3 commits when i posted them to github already? all 3 say first commit i want to change them. :)
@AG-im3dz
@AG-im3dz 3 жыл бұрын
Hi Eric, so the second editor appears automatically right after you :wq the first editor? Thanks,
@phette23
@phette23 3 жыл бұрын
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.
@AG-im3dz
@AG-im3dz 3 жыл бұрын
@@phette23 thanks !
@jaydraws2019
@jaydraws2019 4 жыл бұрын
God level tutorial. You saved me hours of headache :)
@prateekchourasia8031
@prateekchourasia8031 4 жыл бұрын
Thanks man! Thanks a lot! I was shit scared because I was going to undo the commit for a month work xD
@jaydraws2019
@jaydraws2019 4 жыл бұрын
Thank you so much.
@ismailkassim6325
@ismailkassim6325 4 жыл бұрын
At 2:13 when you wrote the commit, how did you get to the buttom? edit* Fix the issue. Press shift and colon( : ) at the same time -> shift + :
@99Boiko
@99Boiko 4 жыл бұрын
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).
@uraniumspoon4497
@uraniumspoon4497 4 жыл бұрын
And to think I spent hours reverting vandalism every day...
@alexandersheppard1997
@alexandersheppard1997 3 жыл бұрын
Your work is useless. We will vandalize faster than you can fix them!
@uraniumspoon4497
@uraniumspoon4497 3 жыл бұрын
@@alexandersheppard1997 how old are you?
@BukuiZhao
@BukuiZhao 4 жыл бұрын
One way you can fight vandalism is by using recent changes, I have a video but unfortunately it's not uploaded to KZbin yet reverting edits that say needs review and like today I've reverted like 20 so far
@BukuiZhao
@BukuiZhao 4 жыл бұрын
I reverted another vandalism before that bot got chance to detect that vandalism just today
@debdulalsutradhar5767
@debdulalsutradhar5767 4 жыл бұрын
Hello can you teach me how to do it? I'm in trouble please
@BukuiZhao
@BukuiZhao 4 жыл бұрын
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
@BukuiZhao
@BukuiZhao 4 жыл бұрын
@FANTOM X6 Sutradhar another one is this diff en.wikipedia.org/w/index.php?title=Dagupan&diff=969596678&oldid=969596573&diffmode=source
@cyorbea
@cyorbea 4 жыл бұрын
You rule man!!
@ahmeda5110
@ahmeda5110 4 жыл бұрын
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.
@jacklol72
@jacklol72 4 жыл бұрын
Oof
@prashansagupta1596
@prashansagupta1596 4 жыл бұрын
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?
@phette23
@phette23 4 жыл бұрын
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.
@phette23
@phette23 4 жыл бұрын
Oh it actually needs to be Escape (to exit Insert mode), then colon wq. So altogether it's- ESC : w q
@prashansagupta1596
@prashansagupta1596 4 жыл бұрын
@@phette23 thank you so much. This helped me a lot :)
@sergelachapelle7992
@sergelachapelle7992 4 жыл бұрын
Thank you! This helped me a lot...
@LignariusDM
@LignariusDM 4 жыл бұрын
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!
@phette23
@phette23 4 жыл бұрын
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.
@LignariusDM
@LignariusDM 4 жыл бұрын
@@phette23 Thanks for the reply, I'll give this a try!
@avimehenwal
@avimehenwal 5 жыл бұрын
I am using rebase a lot lately ... thankyou *Y(
@harrisandreson
@harrisandreson 5 жыл бұрын
why don't you upload more and more videos, you have good knowledge
@shrikantamazumder3268
@shrikantamazumder3268 5 жыл бұрын
Thank you
@andrewmriv
@andrewmriv 5 жыл бұрын
Thank you for this! Worked like a charm
@mazharabbas871
@mazharabbas871 5 жыл бұрын
Thanks, this is really helpful. +1