Learn GitLab in 3 Hours | GitLab Complete Tutorial For Beginners
HTML-код
- Опубликовано: 31 май 2024
- This GitLab tutorial will teach you everything you need to know about GitLab.
Start FREE testing: accounts.lambdatest.com/regis...
Integrate & Automate Selenium Test Suites with GitLab CI: bit.ly/2Y3ke3R
In this Complete GitLab CI Tutorial, Moss(@tech_with_moss), an expert in DevOps and CI/CD tools, deep dives into Git commands, navigates you through GitLab Interface, and helps creating a GitLab pipeline in detail.
By the end of this video, you will learn -:
◾ What is GitLab CI?
◾ Introduction to GitLab Interface
◾ What is GitLab Workflow?
◾ What is GitLab Flow?
◾ How does GitLab CI work?
◾ How to use GitLab Flow in GitLab Project?
◾ What is GitLab Pipeline?
◾ How to create a GitLab Pipeline?
◾ How to Migrate from Jenkins Pipeline to GitLab CI?
◾ What is GitLab Registry?
𝗩𝗜𝗗𝗘𝗢 𝗖𝗛𝗔𝗣𝗧𝗘𝗥𝗦 👀
0:00:00 - Introduction
0:02:43 - What is GitLab?
0:03:08 - What is Difference Between Git and GitLab?
0:03:39 - Why use GitLab?
0:04:06 - Basic Commands of GitLab
0:38:16 - The GitLab Interface
1:16:57 - GitLab Flow in Practice
1:55:39 - CI/CD in GitLab
2:32:29 - Migrating to GitLab CI/CD
3:11:01 - GitLab Pipelines
3:26:03 - Conclusion
𝗖𝗢𝗠𝗣𝗟𝗘𝗧𝗘 𝗧𝗨𝗧𝗢𝗥𝗜𝗔𝗟 𝗦𝗘𝗥𝗜𝗘𝗦 👌
Introduction to GitLab CI | What is GitLab CI | Part I
bit.ly/3kbmsq8
Introduction To GitLab Interface | Part II
bit.ly/3og6Rbz
What Is GitLab Workflow | GitLab Flow | Part III
bit.ly/3Fd2jIN
How To Use GitLab Flow In GitLab Project | Part IV
bit.ly/3lPC2Zt
What is GitLab Pipeline? | How To Create GitLab Pipeline | Part V
bit.ly/3jRt5xy
How to Migrate from Jenkins Pipeline to GitLab CI | Part VI
bit.ly/3HF5fPT
What is GitLab Registry? | GitLab Pipeline | Part VII bit.ly/3dwadjZ
𝗜𝗡𝗧𝗘𝗚𝗥𝗔𝗧𝗘 𝗟𝗔𝗠𝗕𝗗𝗔𝗧𝗘𝗦𝗧 𝗔𝗡𝗗 𝗚𝗜𝗧𝗟𝗔𝗕
👉🏻Easily mark and track bugs with LambdaTest GitLab integration when performing cross browser testing on LambdaTest platform.
👉🏻LambdaTest provides testing environment information, additional testing screenshots and videos.
Integrate GitLab with LambdaTest: bit.ly/3ti02GM
𝗟𝗘𝗔𝗥𝗡𝗜𝗡𝗚 𝗛𝗨𝗕 🎫
◾ Top CI/CD Tools comparison: bit.ly/3CPkyC5
𝗦𝗨𝗣𝗣𝗢𝗥𝗧 𝗗𝗢𝗖𝗨𝗠𝗘𝗡𝗧𝗔𝗧𝗜𝗢𝗡 📌
◾ GitLab CI Integration with LambdaTest-: bit.ly/2WWqXvv
◾ GitLab Integration -: bit.ly/38J7Mbp
◾ Integrations With CI/CD Tools -: bit.ly/3nzVkTV
*𝑹𝒆𝒍𝒂𝒕𝒆𝒅 𝑩𝒍𝒐𝒈𝒔*
◾ How To Use GitLab CI for running tests Locally? -: bit.ly/3DPV5tF
◾ CircleCI vs. GitLab: Choosing The Right CI/CD Tool -: bit.ly/3n5X07j
◾ Jenkins vs. GitLab CI: Battle of CI/CD Tools -: bit.ly/3n5ycwk
◾ Build An Automated Testing Pipeline With GitLab CI/CD & Selenium Grid -: bit.ly/3DJduIu
◾ LambdaTest One-Click Integration With Bitbucket and GitLab -: bit.ly/3ufEaMz
*𝑹𝒆𝒍𝒂𝒕𝒆𝒅 𝑾𝒆𝒃𝒊𝒏𝒂𝒓*
◾ Ensure A Robust CI/CD Pipeline With GitLab CI & LambdaTest-: bit.ly/3h3gKF6
Sign Up for LambdaTest. It’s 🅵🆁🅴🅴 ⛳
Conduct live interactive cross-browser compatibility testing of websites and web apps on latest mobile and desktop browsers: bit.ly/3lNWpVF
Register Now to Avail Bonanza Offerings 💎
+ Test website on 3000+ mobile and desktop browser environments over LambdaTest cloud
+ Online scalable Selenium Grid to perform Manual testing as well as Automation testing
+ 100 minutes of free automated testing
+ Sessions with 10 Minutes of Each Free Live Interactive testing per month
+ 10 Responsive Testing (Test a page across 56 Device configurations with a single click)
+ 30 minutes of free testing on LT Browser
For questions: Support@lambdatest.com
*𝑬𝒙𝒑𝒍𝒐𝒓𝒆*
🎬 Most Recent Videos: bit.ly/3kUUeAQ
🎓 Learn More At LambdaTest: bit.ly/3fr6l4Z
🎥 LambdaTest Customers: bit.ly/2TB7pvD
🚀 Webinars: bit.ly/37i41co
🛠️ Product Updates: bit.ly/3717NGO
💬 LambdaTest Certifications: bit.ly/3x4EtcY
📢 FREE For Limited Time Only 🕑, Enroll Now!
*𝑺𝒐𝒄𝒊𝒂𝒍*
📝 BLOG: bit.ly/3yGVsUc
👥 COMMUNITY: bit.ly/3Aiz5oO
🔴 NEWSLETTER: bit.ly/3juhxzc
🖼️ GITHUB: bit.ly/3jowfYs
🛠️ RUclips: bit.ly/3rH2Yfh
🌎 LINKEDIN: bit.ly/3xA6F84
👥 FACEBOOK: bit.ly/37mbQOa
🐦TWITTER: bit.ly/3Cn0g3A
📸 PINTEREST: bit.ly/2VCXI05
#cicd #gitlabci #gitlab #gitlabcicd #gitlabpipeline #tutorial #developers #software #gitlabtutorial #lambdatest #automationtesting
Disclaimer:
This video features materials protected by the Fair Use guidelines of Section 107 of the Copyright Act. All rights reserved to © 2021 LambdaTest. Any illegal reproduction of this content will result in immediate legal action. 
Наука
Proof that anything can be learned today and its because of incredible resources such as this one. Thank you for doing this
Glad you liked it!
Absolutely great tutorial. Very well structured, and all concepts explained clearly with hands on examples. Thanks!
Glad you enjoyed it!
This course is exactly what I was looking for.
Thank you.
Hope it helps Neil :)
BEST Gitlab training ever. So in depth and precise. Thank you so much!
Glad it was helpful!
Subscribe, and look forward to more such tutorials! ✨
This is a masterpiece! Thanks for your time and generosity to help others! You shall be rewarded, all the best
Much appreciated!
This is brilliant, I needed to get up to speed with Gitlab this week and this tutorial has ticked all the boxes!
Great to hear!
This is a tutorial for beginners who already understand what a shell/terminal is in general, what version control is, and what git is. Otherwize, at 7:15 I am happy to think that I can follow it so far.
Great to hear you're following along well! If you have any questions, feel free to ask.
Don't forget to subscribe the channel for more such videos.
To make tutorials for beginners is very hard: many things 'trivial' for the teacher are not known by the learner at all. The teacher is usually unaware of this. These are usually concepts. At 46:56 is the very first time you actually mention what this whole authentication is all about: you want the Git client to access GitLab in the backround, and use this connection to upload commits !!!! I suppose you can use 'git config' in the Git client terminal window to set up access to GitLab. This has never been said out loud up until this point. However, I do appreciate the hard work put into the video, it is very useful! Thank you!
Thank you for sharing your feedback! We understand that explaining concepts can be challenging, especially for beginners. We appreciate your understanding and are glad to hear that you found the video useful.
By far the best tutorial I have seen for Git. So much clarity and intuition! Much Appreciated.
Glad you found this helpful😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
Starting a new job where gitlab is a mainstay (Have zero CI/CD or repository experience) so this tutorial is very appreciated. Thank you!
Hey Josef👋🏻
You're very welcome! Glad it was helpful! 😇
Just started the course. Really looks like a great course.
I just stumbled onto this channel, and so far, I think it is one of the best
Thank you so much for your kind words.
Please subscribe to our RUclips channel for more such videos 🌟
I was completely new to the Git and this video really helped me to learn the git concepts and I made a notes for myself which is helping in my daily work. Good job man!!
Hey Sampath 👋
Glad it helped!
Just wanted to learn about GitLab flow and this tutorial was perfect for that. Thank you so much!
Glad it was helpful!
Many thanks for this tutorial Moss. That was really helpful. Good Job!
Hey Yecine👋
Glad you enjoyed it!
Man your video is one of the best in youtube, following along those hands on I already felt I am a semi pro Devops engineer lol, thanks for this awesome contrubition to the already complex tech world!
Thanks Frank! Great to hear
Amazing and simple demonstration. Every single part is explained perfectly. Go ahead, well done.
Glad it was helpful!
You saved the day. Honestly i dont find time to do videos with what i know but i learn what i dont know alot from videos. After watching this your video i asked myself that if everyone is like me how will the knowledge get out there. Ive learned alot from you and i have decided to also start sharing. Thanks for the inspiration
We're thrilled to hear that you found the video helpful and inspiring!
Thank you for your kind words! 🚀📘
Your decision to start sharing your knowledge is commendable, and We're sure many will benefit from your expertise. Remember, every expert was once a beginner, and every educator started as a learner. ❤️
I've learnt GitLab recently and your tutorials are really helpful. I watch many other tutorials but they're not detailed and easy to follow like yours. I really appreciate. Thank you very much.
Hey Lee, Glad they are helpful to you
This is the best tutorial on GITLAB concepts. Thank you Moss
Glad it was helpful!
I love your method to teach. Anyone can easily understand. Thank you for making a video.
Glad it was helpful!
This is one great and very comprehensive tutorial for Git/GitLab beginners. Excellent work Moss.
Glad you liked it, Please subscribe to our channel for more such tutorials.
Thanks mate, appreciate the work you put in to create these
Glad you like them!
this video is how I got to know your channel. Subbed, thank you!
next time, could you please consider doing a full ci/cd course, as I like the way you do and explain things pretty much easily
Hey there 👋🏻
Glad you liked it. Thanks for the suggestion. Stay tuned⚡
Very very good tutorial, helped a lot with the Gitlab basics. Gave up at the CI/CD point and maven installation, a bit too much for me now.. Nice English easy to understand for those who not native
Thanks EML, Glad you liked it
Excellent tutorial! Thank you for your efforts and such a nice video!
Glad it was helpful! 💖
Best explanation of Gitlab and git on youtube. Thank you
Glad you liked the video,
Please subscribe to our RUclips channel for more such videos 🌟
Thank you so much, I have learned so much for watching this video!!
Thanks Kuo-Liang Chang. Glad it was helpful
Amazing work and dedication!
Glad you liked this😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
Wow, it was very clearly explained and got to know many things about hitlab...Thanks for sharing!!
Glad it was helpful 💖
Very good video, all the basics have been covered very well.
Glad it was helpful!
Thank you so much for the basic git section of the video!
Glad it was helpful! 🙂
Thanks for simplifying Git and GitLab, well explained.
Glad it was helpful!
Thank you very much! I like this step by step tutorial!
Glad you liked it 😊
Subscribe to our channel for more such tutorials! ✨
Thanks for making this video, really good and helpful!
Hey Bryan 👋
Glad it was helpful!
Thanks for uploading this.I will follow your videos to learn more about gitlab.
We're delighted that you found this valuable! 😊
Don't forget to subscribe to our channel so you won't miss any updates on our upcoming tutorials! ✨
This video is a life saver. Thanks for the efforts :)
Glad it helped!
Adorable Tutorial . Thank you for sharing this
Glad you liked it!
Do subscribe the channel for more such video tutorials
This is amazing mate. Thank you!
Glad you liked it!
Subscribe, and look forward to more such tutorials! ✨
@@LambdaTest already done. Really appreciate it
Very well explained. Thank you for this wonderful tutorial.
You're very welcome! Glad it was helpful! 😇
Great tutorial! Very well explained!
Thanks for the feedback! 🙌
This is just a pure gold what this MAN shared with us
Thanks Ilya
Subscribed, so clear and precise.
Glad you liked it! ✨
Its a master piece. All got well explained..
Thanks Nimalan, Glad it was helpful
This is a beautiful course !
thanks Arish
Excellent!! thanks for sharing this tutorial
Glad it was helpful!
Thank You For this Awesome Tutorials , Really helpfull !.
Glad you like them!
Really an excellent resource to go through for gitlab.. Thank you #LambdaTest
Glad you liked this😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
This was exactly what i needed
Thanks Cradical!
Clear and concice. Thanks alot
Glad it was helpful!
Amazingly explained
Glad it was helpful!
liked and subscribed. hope your channel grows brother
Thanks for the sub!
Great explanation ! :)
thanks Jan!
5 Stars, Thanks Moss
Glad you liked it!
Please subscribe to our RUclips channel for more such videos 🌟
Your videos are awesome :) Thank you
Glad you like them! 👋
this is really an amazing tutorial
Glad you liked it!
Please subscribe to our RUclips channel for more such videos 🌟
Bro.. you are the best of the best
Thanks Chandan
Marking where I left off: 1:27:08
Thanks !! It's very useful !!!
Glad you liked it!
Subscribe, and look forward to more such tutorials! ✨
Nice video. Great job!
Hey there, Thanks for your kind words😇
Make sure you subscribe to our RUclips channel for more 👋🏻
partially great tutorial - good job
Many thanks!
very very fruitful, thanks.
You are most welcome
Great video!
Glad you liked it!
Please subscribe the channel for more such tutorials🌟
Well done bro...thanks a lot
Thanks and welcome
Thank you!
Glad it was helpful.
Please subscribe to our RUclips channel for more such videos 🌟
Great Tutorial!
Glad you liked it! 🙌
Great! Thank you Bro
You're welcome!
Great tutorial!
Glad you liked it 😇
Make sure you subscribe to our RUclips channel for more 👋🏻
awesome content
If you opt for Git, consider choosing an intuitive GUI to accompany it. Using Git on the command-line can cause nightmares, especially in the beginning. The commands in Git are long and come with multiple options, which increases the difficulty.
Thanks for sharing your perspective!
However, once mastered, it provides powerful tools for collaborative development. To mitigate potential issues, teams can establish guidelines, use Pull/Merge Request reviews, and integrate continuous integration tools. Also, there's a vast community and numerous resources available to assist with Git education.
WHAT IS THIS ?!!!! U ARE AWESOME DUDE
Thanks 😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
Great Initiative
Thanks AlaDin
great stuff man
Thanks Randy
very very well explained
Glad you found this helpful😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
I liked the way you teaching
Thank you Muhammed. Glad you liked it✨
Thrilled to see someone using vim.
High five 🖐🏻
Amazing
Glad you liked it!
Please subscribe to our RUclips channel for more such videos 🌟
Great content 😊
Thank you 😁, Glad you liked it
Hi cool&perfect
Thanks a lot 👍
Glad you liked it!
very good quality:)
Glad you think so!
@@LambdaTest greetings from Poland:)
Thank you for most interesting and valuable session . I just wanted to know how can send a email notifications prior to build failure when pipeline got failed using Gitlab API.
Hey Rajkiran,
You can check out the steps of configuration on this blog docs.gitlab.com/ee/user/project/integrations/pipeline_status_emails.html
The best video for Gitlab in the entire RUclips 😅
We're delighted that you found it helpful! 😊
Don't forget to subscribe to our channel for the latest updates on upcoming tutorials! ✨
Just one word RESPECT
Thanks Muddassir,
Glad you liked it 💖
By the way, for switching to a branch, you should use the "new" switch command, instead of "checkout"
Yes, correct
The git switch command makes it clearer that the purpose is to switch branches, while git restore is meant for restoring working tree files. This is part of an effort to make Git commands more user-friendly and to reduce the overloading of the checkout command.
Hi Moss, excellent video. Learning a lot from this. I had one question
1. When we closed the issues, don't we have a capability to link the commit to the issue (or when we raise a commit, tag it to an issue)? Without that, closing the issue/marking it as done would lead to lack of traceability
Hi Ashvin, Glad to hear that.
For your question, let us get back to you
@@LambdaTest Thanks for the response. I did some experiments with gitlab. What I found was that if you put the commit ID in the comments, then gitlab automatically creates a hyperlink to the commit.
I think with this, we can easily track the commit that was responsible for the issue to be closed.
Hey @@ashvinla, There are several ways to mention an issue or make issues appear in each other's Linked issues section. Please also have a look at this documentation docs.gitlab.com/ee/user/project/issues/crosslinking_issues.html
I'll be honest got a bit lost at the CI/CD section, anyone got any recommendation on how I can learn that better
can u pls explain how to override variables in application.properties or just use gitlab variables in maven project
You can try setting the Environment Variables in your Project -> Settings -> CI/CD -> Environment Variables and also in the .gitlab-ci.yml file
how to sync merge request with target branch ? i have tried doing "git pull origin master"
it was successful but when I pushed it shows commit from others as well in my merge request.
Hey there,
To sync your merge request with the target branch without including commits from others:
Fetch the latest changes: git fetch origin
Rebase your feature branch onto the target branch: git rebase origin/target_branch
Force push your updated feature branch: git push origin your_branch_name --force-with-lease
This will align your branch with the target branch without mixing in other's commits. Ensure you coordinate with your team before force pushing, as it can overwrite changes.
Thanks for the video! I have a question: i've added and modified a simple txt file and pushed to gitlab. Then created a merge request and went to "Changes" section to compare what i've changed in the added file. But i don't see content of the file, instead i see the message: "File suppressed by a .gitattributes entry or the file's encoding is unsupported.". I've tried adding ".gitattributes" file and populate it with "*text=auto", but that seems not to work. Do you have a solution for that?
Hey Artem,
To resolve the issue of GitLab displaying the message "File suppressed by a .gitattributes entry or the file's encoding is unsupported" when comparing changes:
- Verify the .gitattributes file in the root directory of your repository and ensure it contains the correct configuration, such as * text=auto for handling text files automatically.
- Check the encoding of the text file you added and modified, ensuring it is UTF-8 encoded. Convert the file to UTF-8 if necessary.
- Clear the GitLab cache by navigating to Settings > Repository > Remove artifacts.
- Confirm that you are using an up-to-date version of GitLab.
If the issues persists, please reach us out at support@lambdatest.com
Hi Moss, great video! Quick question on the Maven pipeline, it's throwing an error that its unable to find the .m2/repository path. I did verify its under C:\users\\.m2 repository. Any thoughts?
Hey miguelv, let us get back to you on this
Miguelv, Please try setting the maven path variables on job level rather than the pipeline
@@LambdaTest Thank you. I'll give that a try.
Actually: Adding the maven options in addition to the maven CLI options to the mvn commands fixed it for me: mvn $MAVEN_CLI_OPTS $MAVEN_OPTS
how do you get your commands to show up beside your user line? my command line has the $ and user input below, making each action take 2 lines before the output instead of 1, which I find a bit gross to look at. Where did you go to change this?
Hey there,
Here's a concise guide to modifying your command prompt so that user commands appear on the same line as the prompt (e.g., user@host:~$ command), instead of having the $ and command on separate lines:
Open Your Shell Configuration File: For Bash, this is typically .bashrc or .bash_profile in your home directory. For Zsh, it's .zshrc. Use a text editor to open it, like nano ~/.bashrc or nano ~/.zshrc.
Modify the PS1 Variable: The prompt is defined by the PS1 environment variable. You'll see a line in the configuration file that starts with PS1=.
Customize PS1: You can customize this variable to change how your prompt looks. To have your command appear on the same line as your prompt, make sure your PS1 variable does not include
at the end.
adds a new line.
Example for a simple prompt: PS1='\u@\h:\w\$ '
- \u represents the username.
- \h represents the hostname.
- \w represents the current working directory.
- $ is the symbol for your prompt, followed by a space to separate the command.
Wow that’s awesome! Thanks so much!
Great explanation
Could you make a video about how two people can work on git with 2 branches?(same file)
Because I was getting problems. If two people are working with same file on 2 different branches then they will get error (let first person changed file then ....git merge... Then push -u origin.... This will be executed but second person who is working with same file on different branch (at the same time) and if he tries to push then he will get an error.
Please resolve this issue.
Glad you liked the video!
Thanks for the suggestion, and look forward to more insightful videos! 🙌
alias virtue_signal="git config --global init.defaultBranch main"
I’m learning this to diversify my skills as a self-taught front end developer. If I don’t have access to gitlab, can I still continue this course using a free trial gitlab account?
Hi Aznim, Let us get back to you on the same
You are awesome
Thanks Kelvin!
@@LambdaTest Do you have more comprehensive tutorial on GitLab CI/CD? Just GitLab, Jenkins excluded?
Kelvin, we didn't get you. Do you mean to say tutorials other than GitLab and Jenkins?
@@LambdaTest I meant a comprehensive tutorial on purely GitLab CI/CD that could offer a deeper understanding of GitLab pipelines.
@@kelvinmuriithi You can go through the complete playlist having different chapters around: ruclips.net/p/PLZMWkkQEwOPmGolqJPsAm_4fcBDDc2to_
Introduction to GitLab CI | What is GitLab CI | GitLab Tutorial For Beginners | Part I
Introduction To GitLab Interface | GitLab Tutorial For Beginners | Part II
What Is GitLab Workflow | GitLab Flow | GitLab Tutorial For Beginners | Part III
How To Use GitLab Flow In GitLab Project | GitLab Tutorial For Beginners | Part IV
What Is GitLab Pipeline? | How To Create GitLab Pipeline | GitLab Tutorial For Beginners | Part V
How To Migrate From Jenkins Pipeline To GitLab CI | GitLab Tutorial For Beginners | Part VI
What is GitLab Registry? | GitLab Pipeline | GitLab Tutorial For Beginners | Part VII
You can also go through our blog on How To Build An Automated Testing Pipeline With GitLab CI/CD & Selenium Grid: www.lambdatest.com/blog/automated-testing-pipeline-with-gitlab-ci-cd-and-selenium/
Why there is no a ‘I love’ ❤ button?
I dont only like it … thank you so much. It is quite complex for me and this video helped me.
Thank you! 😃
12:06 what did you do after typing "hello!"? I'm stuck at this part.
Hey there,
Here the commands:
1. vim hello.txt: Opens the file hello.txt in the Vim editor, creating it if it doesn't exist. Vim is used for editing text and has multiple modes, like insert mode for typing and normal mode for commands.
2. ls: Lists the contents of the current directory, showing files and directories. You can use options to get more detailed information.
3. git status: Shows the current status of a Git repository, including changes staged for commit, modified files not yet staged, and untracked files. It helps you manage and review changes before committing.
What is the benefit of the Gitlab workflow vs the Github workflow? I struggle to see the practical benefits of a separate staging branch. If the code is the same the behaviour will be identical.
Hi Shahe, Let us get back to you
Hey there, the biggest difference between GitLab Flow and GitHub Flow are the branches of the environment in GitLab Flow (for example, pre-production and production) GitHub flow assumes that if you are on the master you can go to production. GitLab flow allows the code to pass through internal environments before it reaches production.
Stagging branch contains the code that is being tested before going to production ie. we use this branch to deploy to a production-like environment that worked as a final test until production, this environment is also called staging
Hi MOS, I have one strong doubt, using cicd pipeline on which application server our artifact is getting deployed?
Hi Wasim, let us get back to you
Hey Wasim 👋🏻, GitLab maintains and provides a full history of deployments and environments. Please have a look at this documentation docs.gitlab.com/ee/ci/environments.
Let us know if this help :)
Hi Moss, I am not a software person but I work with software people that speak coding. I am trying to learn software speak. I don't know how to do basic things like verifying which version of Git I have on my computer. Is that a command screen you are using to do that? I thought this is for beginners but maybe you have to already know how to do some things first.
Hey there,
No problem at all! You'd check your Git version via the 'command-line interface' or terminal. Just open it and type git --version and press enter. If Git is installed, you'll see the version number. If not, you'll see an error. The initial learning curve in coding can feel steep but don't hesitate to ask questions. We all start somewhere!