Відео

HOW TO FIX THIS WITH DOCKER DIND INSTANCE BASE GITLAB RUNNER WITH GITLAB-CE USING DOCKER EXECUTOR docker build -t $CI_REGISTRY_IMAGE:$SEMVER . ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Cleaning up project directory and file based variables 00:00 ERROR: Job failed: exit code 1

thank you, very informative walk through!

What's the terminal theme ur using?

What theme are you using in your terminal? I'm guessing it's iterm with oh-my-zsh? Great tutorial btw, will def revisit this one again

how would you go around having many commits.. as the rebase goes step by step.. you'll have to redo the same conflict resolution many times

Bro, this is such a good explainer. Been going through trying to learn git better and you helped a lot.

sir can you show what would happen if we do the rebasing on open repository as you said in video

Great video

thanks for the explaination sir

This is when you made one change to the file. Sometimes we make multiple changes/commits on branch. When rebasing I get promoted to accept current or head changes. I accept and continue, then it ask me to do same in the next commit. Is this normal?

Thanks for clean explanation.

I just subscribed thanks Zuckerberg!

the screen is cropped at the bottom

Could you please give me a chance to work with you online (remotely)

U menya vse ravno stoit "first resolve merge conflicts", which I of course did, I am not a beginner. Did it serveral times without luck, still the same error. Never used rebase and had to

0:47 must have hurt

Same problem as every video on the internet- some abstract diagram. Not a real story of what the code and problem looks like.

I feel like he is struggling to not blink horizontally

I watched this video after having some difficulty with a git rebase and the video photo perfectly captured my feelings after working with the rebase.

Awesome tutorial. Thank you. Now I can fix my mess.

When you are rebasing the commit the HEAD is detached so how to push the changes to the remote?

thank you, bro. Watched your video after wasting 6 hours. I was just pushing using VS code after rebasing not force pushing. I almost quit programming. thank you so much

Great video

I had a situation where I could not force push the changes after I fixed 5 commit conflicts which ended by one of the commit going missing as there was no difference. Maybe that's why force push didn't work. So I rebased pulled from my remote feature branch to my local branch and I had to fix things all over again and it was pretty different. After fixing conflicts now it has become crazy and full of other people's commits. I'm now thinking of creating a new branch from my current updated main branch then add my changes manually from my old feature branch since I don't want to deal with what's going on there it's messed up!

Hi Can you publish all command line for the the setup ?

did you miss the rbac section in values file ? its rbac or serviceaccount name

Isn't force push a bad strategy?

"Make a copy of your local repo before rebase", or maybe just make a new branch and reset to it if you messed up the rebase.

main vs master . ahahahahha epic reference . awesome video. thanks

The best one ever!

The best video on rebase on youtube ! Thanks a lot man !

Really loved your video nice work bro

Very nice job explaining and teaching setting up microk8s on ubuntu for Gitlab CI runners. Going to share this with workers.

👍

If you find this useful and/or entertaining, please consider buying me a coffee :) www.buymeacoffee.com/teamprogrammer This helps support this channel and lets me make more explainer videos in the short term.

Thank you for this video!

Love your way of explaining. The practical eyample really helps

Thank you so much, sir! For explaining this topic of rebasing with merge conflicts so well. I have watch many other videos. This is the clearest. I just used it to rebase and solve conflicts by myself for the 1st time! I thought I could never learn to do this by myself. It feels good to not have to plead my male colleagues for help with this all the time.

Thank you, this helped me a lot.

The king is back!

ribs hurt from laughing so hard

THANKS man. Keep going and make more videos !!

I did that but there is a loop

Thanks!

Thank you for this video! It's helpful to just see you go through the steps and pause to explain what we're looking at frequently, and why we're seeing the step we're at. This is a great approach and makes it much easier to learn than reading documentation in some cases.

af 😀

Are you git god?) Very helpful!

I understand now!!! ahh, best feeling ever, Thank you!!

Even though I barely understood what's being discussed I enjoyed it.

This was useful... please keep up the good work!