New Git Users Be Like...

[@MrPSolver]

git commit -m "Subscribe for more Billy : ) "

[@n3bul0n]

Everybody: git is simple Billy: Where is my pen and paper?

[@fernabianer1898]

How about giving Frek a new tiny detail? He pushes people to subscribe to his YT channel anyways, so why not let him sneak in a link that's the exact same link needed to subscribe to your YT-Channel when ever he contributes some code to Billy or the company? Would be a nice and easy easter egg + there is certainly some people watching your videos who want to try the link when they spot it

[@szilardfineascovasa6144]

I just did, man. Quality!

[@HomoErectusIsAFunnyName]

Imbecile What kind of message is that? Listen, Child: The commit contains the following structural elements, to communicate intent to the consumers of your library: fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning). feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning). BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type. types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others. footers other than BREAKING CHANGE: may be provided and follow a convention similar to git trailer format. Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.

[@n3bul0n]

@@HomoErectusIsAFunnyName Dude, this is supposed to be something funny... 🤦‍♂

[@sp1r14ual]

- Wait. What branch are you on? - The top one

[@realdragon]

True bird chad

[@HibiTeamQueso]

Based

[@dev_time]

xDDD

[@Love4Hardstyle]

Sounds like my first year of programming lol. It felt so complicated seeing all those branches but I was just making myself crazy and nobody could explain it in a calm way to me. Couple months later I got used to working on dev because I was the only one on the projects and I comitted without review to master straight away. Now at my New company we have at least 1 other guy checking the code and branch protection enabled. + I know how branches work now lol. Still have to start using terminal one day though because right now Im using github desktop.

[@theseangle]

@@Love4Hardstyleyeah you definitely should learn CLI (terminal), the earlier - the better

[@bobnobrain]

I like how Alan finds the birdpic even before it is actually pushed to remote

[@zwykyziomek2570]

Exactly why is nobody talking about this lmao

[@h3nry_t122]

My guy took his laptop

[@cye2310]

@@h3nry_t122 spyware is actually God

[@felipef1nn40]

TeamViewer maybe lol

[@filiformis]

Alan is always coming over to Billy's desk and peeking at his screen.

[@thewalkthroughmaking]

I'm ashamed to admit that I actually gasped when I saw him typing '--force' XD

[@rngesus8057]

pfft git add . git commit --amend --no-edit git push -f or gitfo

[@thewalkthroughmaking]

@@rngesus8057 Some people just want to see the world burn

[@ImmacHn]

That's a proper reaction.

[@vanilla4064]

@@rngesus8057 at least use -force-with-lease 😭

[@ihateidiots9484]

The problem is that git devs created the --force option and now tell everyone not to use it

[@Excalibaard]

Most believable part is where corporate decides that devs should keep track on paper (don't forget to include the 10 lines of code you're most proud of!)

[@kosmonautofficial296]

Yes hahahh

[@zankaa8031]

Holy shit yes. One thing goes wrong with a piece of software and regardless of what the user did wrong the problem is always the tool that makes your job 100x easier instead of the person who doesn't know how to use it.

[@johnpage4853]

We once had a really old school coworker. He was probably already coding, when computers still were the size of houses and had like 2 bytes of memory. Every time he finished a task, he would print out the source code and marked the lines he changed with a text marker. I'm not making this up xD

[@kosmonautofficial296]

@@johnpage4853 wow haha

[@Eternal_Otter]

@@johnpage4853 Well that's what I like to call "stuck in time". He probably was used to do that back then.

[@xZaapKaT]

the shregory and billy dynamic is too elite.

[@szilardfineascovasa6144]

It's "3l33t", plz. Noob. (Shregory voice...)

[@DrGandW]

Shregory is the yang to Billy’s yin

[@szilardfineascovasa6144]

I wonder is Shregory has anything to do with his love for sh, being a developer rockstar ("shredder") or it's just a subtle hint that he is a 6 feet 7 shredded 1000$ a day CEO sherdogger. Looking forward to seeing his character expanded.

[@abuabdullah9878]

Yeah, Shreg is honestly a great mentor

[@Quid231]

Alan: ''We'd rather have you compute the sum of the first 10 integers cubed, not squared.'' Billy: ''Fine, might take me another week tho.'' Spoken like a true programmer.

[@sanderdejong66]

And it will take him a month

[@remboldt03]

I actually learned Git through this video. I was sending ZIP Folders the entire time

[@davidwuhrer6704]

git mail is a thing. And so is git archive.

[@lawrencedoliveiro9104]

I’ll give you a point for using .zip instead of .rar.

[@itellyouforfree7238]

@@lawrencedoliveiro9104 I'll take away a point for using .zip instead of .tar.xz

[@lawrencedoliveiro9104]

@@itellyouforfree7238 Don’t be like that. After all, you could lose one for not using zstd compression.

[@gobble_gang]

Holy shit me too 💀 I need git now

The "I like branches" part cracked me up! LOL

[@4everdex]

I honestly don't get why there are no good super easy and understandable tutorials for git(hub). It always feels so complicated, even though it shouldn't be.

[@tung-hsinliu861]

Same feeling bro, been struggling since day 1 and couldn't find a single good tutorial, or maybe I am too dumb.

[@arolimarcellinus8541]

Same here. Looking at git tutorial, feel so demanding just to understand the concept. Programming is already tricky, and they want to add it with git?? How can i teach it to a non IT people that just want to code something but don't like atrocities like Git?

[@theseangle]

There are good tutorials, y'all just lazy. But, alas, not one tutorial fits everybody similarly. Just take a day of your life and you'll get the concept. From there you just consolidate the knowledge, and google everytime you forget something Also, one word: Stackoverflow

[@geowar20]

@@gp6763I used over a dozen software versioning systems over my 44+ years of software development career and never did I have as many problems as with git. Lost changes, lost files, lost time. And before you tell me I was “doing it wrong” I used github desktop which should have hid all the complicated (as in doesn’t actually do what you think they do) git commands behind a easy to understand GUI. I don’t know of any git user that hasn’t on occasion lost hours recovering from git destroying their work. Conclusion: git is an atrocity. TGI’m retired now and don’t have to put up with it any more. That’s one part of my job that I don’t miss.

[@gp6763]

@@geowar20 Use git with GUI => wonder why he loose file xD Yes, you were doing it terribly wrong. I can accept a junior using a GUI for a time. Not an experienced dev. If after 44 years of programming you are afraid of terminals there is a big problem. If you are not but your think using a GUI to control a command line tools is "a good way of doing things" there is an other big problem

[@jblen]

I'm a comp sci student, first used git in a team project second year, then did a year in industry where I properly learned it and thought it was the best thing since sliced strings, vowed to use it even in my own fun projects, then promptly forgot everything and haven't used it since...

[@XenoTravis]

I did that with Linux till I got older and got another job where it wasn't used.

[@ocwebdesigndev54]

the fact that your comp sci courses don't teach you version control is just such a facepalm

[@jblen]

@@ocwebdesigndev54 they told us to use in that team project, and had a very brief 'heres where the docs are, go learn it yourself' speech, but yeah it could've used a lot more emphasis

[@ocwebdesigndev54]

@@jblen To be fair you kind of have to do that in the industry lol. But you're paying them money so that's ridiculous

[@fellowkrieger457]

Don't worry, you will have to remember all of it when being hired. Cause everyone works with version control.

[@jmckendry84]

I started using git a couple of years ago and it has (mostly) made my life a lot easier, however I've never managed to shake off the feeling that I'm using a very powerful tool that I don't fully understand and can cause me serious harm at the slightest accidental misuse.

[@gadget00]

why did it made your life "easier"? Were you there in the days of subversion? why is Git better than svn?

[@soirema]

Same lol, especially whwn you use it as an artist :|

[@n3bul0n]

The problem solver: git push --force

[@peter4210]

if all fails. Destroy the repo and make a new one

[@NostraDavid2]

Also "git reset HEAD~" (just imagine your waifu saying it, ludely)

[@starknights101]

At the same time, a problem maker for the other members.

[@Kkubey]

@@peter4210 Literally did that most of times. Since I was basically completely locked out of the whole project, I just made a new repo every time. After 3 years of trying, I actually gave up on getting it to work when working with others (which are students that also make plenty of mistakes themself). Although I will eventually have to work with it, but at this point I am afraid to try anything.

[@sanderdejong66]

There is no I in Team 😊

[@akramsystems]

alas the daily struggles of beginners are pure gold content

[@heck_n_degenerate940]

You find pleasure in my suffering ;-;

[@aarav6891]

@@heck_n_degenerate940 I find pleasure in my suffering

[@CertifiedCatLover954]

The fact that Frek's changes were 'removes the three stars to make the code work you dingus' and that it was overwritten made me lose it

[@DanRivlean]

0:52 "You push. (edited)" is a nice touch 😉

[@regiwiz]

I don’t get it. Why “(edited)”?

[@greyshopleskin2315]

Why edited?

[@DanRivlean]

If you've worked in an environment where you're supposed to push only when ready for others to review (because PR is up), you'd understand

[@greyshopleskin2315]

@@DanRivlean I don't understand what you said (I'm not native) My workflow is, I do something in a branch created from develop, I can push whenever I want, as much as I want. When I have finished, I create a PR and someone reviews it. I don't understand what you're saying. Could you explain it with other words? I'm curious

[@greyshopleskin2315]

One thing I like, is (as I'm working in a branch of mine) do a lot of small commits and when I finish, use rebase to combine, rename and reorder commits. My commits are a lot better since I do this. Also, it's possible to split commits, or move a portion of a commit to another

[@ithinkimrishi]

Only a true git wizard could get rid of the committed file had me dying. I never figured that out LOLOLOL

[@eonstar]

Restore?

[@Ajx500]

after git add . just run git minus .

[@ItsChris33]

@Eleanor Bartle It picks it up, but it will still be in the commit history

[@Ajx500]

@@eleanorbartle5354 it's not talking about deleting a file, it's about removing a file from a commit to be unstaged. you can use git remove and then a regex or the full filepath/filename, but so many people are used to using git add . where . indicates to commit everything in the current directory, removing a single file is not initially familiar

[@Ajx500]

@@eleanorbartle5354 everything in this video could be looked up, sure. The fun is in looking back at how ignorant we once were.

[@jiriskala]

At the end, I thought Alan would say "We'll record changes using MS Word's track changes."

[@OnceSavedAlwaysSaved7]

Alan “It’s perfect. Some of the best work I’ve seen!” Lololol

[@hansgutenwerke]

Xd

[@hansgutenwerke]

XD 😂

[@neokirito]

Thanks for this, your videos are the more coolest on programming mischief. Really well done and also so funny and real 🙃

[@edberaga]

Please keep making this programming video!! it actually motivates me to learn more and I actually did learn something in every Billy videos!

[@AzoozAlAhlawi]

"record changes on paper" Didn't know Billy and co worked at Twitter

[@LC-hd5dc]

nah twitter records changes _on twitter_

[@useronetwothree-z6f]

the no more using git, we record on paper was funny

[@coolreeb7361]

This video teaches more DevOps in 4 minutes than my CS degree could in 4 years

[@intifadayuri]

I had a course in my uni that was pretty much leaning Git. At first I found it tedious and confusing but learning how absurdly helpful it is to work with a CVS made me fell in love with it.

[@Cyranek]

git rebase -i head~5 --force --tail -p --follow-tags --end-my-life add --all

[@shadowplay1211]

Lol

[@NostraDavid2]

Shregory should've protected the master branch. Also, rename your vars in vscode with f2. Set cursor on var. Press f2. Type new name. Enter.

[@futuza]

It was a policy from management that all programmers have equal access to the repos to "promote unity and shared company culture", he didn't have a choice.

[@wallysonruan]

After a while using GIT: 1. Awesome commit messages, clearer, conventions to help keep it small; 2. Micro commits. Commit after every piece of feature; 3. Trunk based is good, Trunk based is life (kudos to CI/CD pipeline).

[@NostraDavid2]

git add . && git commit -m "magic" && git push Handy for when you're trying to fix your Jenkinsfile. Alternative messages are: "gogogo", "fuck", "revert", and "retry". For context: our PRs get squashed after (before?) merging the code with master, so we can shit talk. It's great.

[@Blast-Forward]

What do you mean by "conventions to help keep it small"? :)

[@wallysonruan]

Last team I joined we had a convention like "[number of the card] type-of-adjustment/resume-of-what-we-did" Ex.: [102] feat/Implemented-new-stuff

[@TheEmolano]

[UPDATE] Temporary Commit

[@exnihilonihilfit6316]

After reading about 750 pages of one Git book, I still have no idea what your last point is about. 😄

[@AceAufWand]

The boss requesting to work on paper at the end make me feel like someone saying: "Let's revert back to ligth by candle, because someone got electrocuted by putting one's finger in a socket" forgetting that using candle could make an entire city brun to the ground.

[@HibiTeamQueso]

This is painfully funny and accurate

[@gorlix]

i honestly love your dedication to this video, you actually made a pretty decent script

[@szilardfineascovasa6144]

This almost made me cry with laughter.

[@Fawstah]

Just getting started with code- I relate to that bird on a spiritual level

[@abhishekparmar4983]

This guy just explained the whole git experience in one discord video😂

[@lampham7874]

the part git push --force is so true for me. I did that as a newbie and my team was like : where did our code go??

[@crateer]

That's why you should never work on the same branch in parallel, else you are literally asking for issues like these which cost you way more time to resolve after all

[@ollielynas5805]

I normally do a big commit when I finish for the day and then like 10 smaller commits to fix small bugs I only just noticed

[@greyshopleskin2315]

I sometimes do the same. But I try to make smalls commits each day and when I finish, I use rebase to reorder, combine and rename commits. So much cleaner

[@lawrencedoliveiro9104]

Just one commit? I ask because normally you tend to work on a bunch of different stuff in a session, which might be more naturally grouped into multiple separate commits. Which is why Git requires an explicit “add” command for making commits, instead of assuming that you want to commit everything that has changed.

[@LC-hd5dc]

@@lawrencedoliveiro9104 time to pull out the next weapon in the beginner's toolbox: `git commit -am .`

[@lukkkasz323]

@@lawrencedoliveiro9104 Yeah, and in case of GUI git, where "add ." is usually automatic, just use stash.

[@atraxisdarkstar]

I've just started with Python and I downloaded Git and I don't have the first clue how any of this works despite multiple tutorials. I too will be recording my changes on paper.

[@sneezydeezymcdeluxe7015]

I only know a little bit about git but this was fucking gold. Please do more.

[@meowmix23]

git commit -m "." - I almost pissed myself from laughing so much

[@nervonabliss]

Why "." bad?

[@v0id_d3m0n]

​@@nervonabliss it tells the other people working on the project (or your future self) nothing about what you changed during that session of work. It's a useless message.

[@lawrencedoliveiro9104]

git commit --allow-empty message -m ""

[@Joneewars2]

git commit -am "asdasadadsa"

[@cnk9822]

Me when my bros push all the "Remove form commit" stuff for the 156th time: 👁️ 👁️ 👄

[@salKinthefirst]

I have to say I'm with Billy on this one, branches are indeed nice

[@deadweight4887]

bro git is the hardest thing as an intern in it's first real job. I still don't know when to git commit or to just amend, always afraid of pulling and breaking stuff too. My code is fine but I messed up my git branch 2 times already and people had to help me. I learned a thing or two but it still scares me to death.

[@crateer]

Haha I feel you, especially in the beginning it can be overwhelming But it's easy: Commit if you made changes you wanna, well, commit. Amend if you committed something and want to add changes to that commit (stuff which should have been committed in the previous commit)

[@sigstackfault]

My FRC team got scared every time they saw a git conflict and _made a new repo._ This happened like five times despite my efforts

[@lot.bajrami]

😂😂😂

[@gasun1274]

jesus christ

[@naakiu]

That was the best, and he didn't change the file name, details, loved

[@iwatchtvwithportal5367]

should have protected the master branch from force pushing in the first place, possibly for the dev branch as well

[@godnyx117]

2:40 "And now! My codebase shall know PAIN!"

[@luckylukeskywalker]

The most frustrating thing about programming team work is when people can‘t just code the way you agreed to but expect you to change your code nonetheless.

[@aj_abdel7113]

Git add -all Git commit -´´.´´ Git push -force 😂 The best practice

[@nervonabliss]

Explain --force

[@janek4913]

@@nervonabliss It ignores all conflicts and forcefully checks your code in which can lead to more serious problems later..

[@somegaydog27271]

--force-with-lease 😔

[@lawrencedoliveiro9104]

Subtle one: git push upstream :«branch» The fact that there is nothing before that colon means the upstream branch is *deleted.*

[@rngesus8057]

@@janek4913 not if ur on ur own branch

[@kokobusa]

I literally laugh the whole video. Thanks for making my day easier bro

[@neil_from_future]

This is what a quick way to introduce to learn a new thing should be, I saw many of beginner mistake in this video that nearly every junior have.

[@TonyRedgrave]

Spyro music? Based. Indeed all of the music and sound effects are A tier.

[@Tivizzz]

Fantastic. Easily one of the best video series on KZbin.

[@otoayana]

1:37 git rebase -i HEAD~1 *change pick to edit* *remove file* git commit --amend git rebase --continue

[@apmcd47]

2:38 "You're doomed." Yep, from the moment he started using git!

[@tigana]

the editing on this makes it pretty funny. you did a good job lmao

[@MikoLotte]

Me watching this randomly added to my timeline while I’ve never used git before: “Yeah paper sounds good”

[@LodeStarYT]

This video just taught me git lol

[@Nailers63]

There is no better feeling than having your code finally be ready enough to push

[@and_rotate69]

I once added an api code file and pushed it to the main branch, i scrapped the internet for how to undo the push, i read every stack overflow thread about it, nothing helped, i ended up deleting the repo and creating a new one

[@aeleron0577]

Well, git is designed that you cannot delete commits (especially not on a remote branch), as it is supposed to track the history of your work. Best practice is probably doing reverts (which does not remove your changes, but commits the negative of the to-be-reverted commit). Maybe you would also get away with git reset. In case you accidentally pushed your private ssh-key, you probably only can resolve this with rebasing. Don't rebase unless you exactly know what you are doing (which you probably won't). Especially when doing it on a remote branch.

[@lnx648]

Yeahhhh, I think every beginner did that. Just revert and push.

[@Ashadow700]

That moment when you just pushed your code, and someone goes "Uuuuhh.... what branch did you say you're on?" F-ing vietnam flashbacks

[@SR-ti6jj]

This is a good beginner tutorial unironically

[@yogxoth1959]

"You contemplate a career at McDonalds." Same, bro.

[@madhurrao6706]

2:41 ALMIGHTY FORCE!!!

[@tamiko_chxn4974]

Actually 1:30 it's still nowadays one of my worst fears at my job lmao, I laughes hard there

[@SpinozicTroll]

I still don't git this...

[@heiscalledinvinciblenotinv68]

As a Git starting user this hits home. I have messed master couple times already.

[@jupitersky]

Watching billy become a programmer has been a joy

[@doodidood]

First day of work: squash everything, commit message: "legacy code"

[@chasecook3854]

We used git for writing papers in latex when I was doing PhD. Advisor would always --force his changes. It was great.

[@jamesgarcia5221]

merge with master and contemplate your career at mcdonalds OMEGALUL

[@maxjenkins6193]

Even shregory admits that pull requests are a nightmare

[@anomienormie8126]

Whenever I write “git -init” I hear a British highschooler say “It’s git, innit bruv?”

[@thanatosor]

The legendary push -force

[@andrewdunbar828]

I was finally able to relax when we got to "paper".

[@skladnayazebra]

I love these Spyro soundtrack bits!

[@780Chris]

Didn’t expect to hear Spyro music lol

[@burtenplays]

This somehow made it more forking confusing.

[@koeiswit]

Love the Runescape music at 1:46

[@knights_limit]

These videos always make me lol 😂 Thank you for making them

[@nintendoloverin9567]

Greetings, good sir. I am in dire need of that Harpsichord part at 2:21 as a full Version.

[@hebermoreno7963]

"I don't commit to anything" sounds like a really nerdy joke. 🤣

[@marcinflisak317]

I'm pretty new to git, and in my job I had to do rebase once... Well... It ended with creating another branch xD

[@cameodamaneo]

I love your profuse use of Spyro music. It's like I'm watching a Dayo video

[@MrPSolver]

Love dayo

[@cameodamaneo]

@@MrPSolver What a small world!

[@faustovii1085]

"We'd prefer some comments within the code to make it easier to understand" "Ok. Might take me another month tho" "But it's just some phrases" "Definetely taking me another month"

[@selfactualizer2099]

I'm saving my brainspace for quantum computing languages

[@BLADDLE]

'listen bird ' idk but I found it hilarious

[@addictedyounoob3164]

the amount of runescape music is 😗👌🔥💯

[@Reeces_Pieces]

Wasn't expecting Wizard Peak here...

[@КалинаВ0505]

I lost it at "sexybird". 🤣

[@austinkim9402]

This is genuinely a good tutorial

[@lordecircojeca2039]

I love how often Spyro music is used here lol

[@santmun]

Liked for the runescape song 😂

[@brawldude2656]

I love how "You push" appears to be edited 💀

[@bobnobrain]

Also Akatsuki theme on 2:39 is amazing :D

[@lawrencedoliveiro9104]

1:52 I just checked, and that’s a real repo!

[@liran3381]

it is hilarious, almost all of the things in this video actually happened to me while I started learning how to use git.

[@FartSIMPson-r6t]

Getlemen, could anybody of you provide me that woneful piece of music which starts at 1:45, please

[@MGMan37]

It's some remix of "Sea Shanty 2" from Runescape

[@spamson7919]

Oh no, again this big brains humor

[@sipinthatbub]

Getting a merge conflict on your last day of work, at 4pm

[@itsbare5172]

How to git… 1: before work pull latest branch, 2. Create new branch for your work, 3 do work… 4. Git STATUS 5. Add the files you actually want to commit(“yes copy and paste the paths”) put a nice commit message and send your PR for your senior dev to nitpick the spacing between your function(: 4 “fixed syntax” commits later and your good