Learn GitLab in 3 Hours | GitLab Complete Tutorial For Beginners

[@josefsieber8377]

Starting a new job where gitlab is a mainstay (Have zero CI/CD or repository experience) so this tutorial is very appreciated. Thank you!

[@LambdaTest]

Hey Josef👋🏻 You're very welcome! Glad it was helpful! 😇

[@renzybi5061]

Proof that anything can be learned today and its because of incredible resources such as this one. Thank you for doing this

[@LambdaTest]

Glad you liked it!

[@miklosbence3852]

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!

[@LambdaTest]

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.

[@miklosbence3852]

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.

[@LambdaTest]

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.

[@wanyuclementclearance3125]

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

[@LambdaTest]

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. ❤️

[@nickrimmer9488]

This is brilliant, I needed to get up to speed with Gitlab this week and this tutorial has ticked all the boxes!

[@LambdaTest]

Great to hear!

[@ManSinhLee]

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.

[@LambdaTest]

Hey Lee, Glad they are helpful to you

[@neilyoungman4250]

This course is exactly what I was looking for. Thank you.

[@LambdaTest]

Hope it helps Neil :)

[@is-gm6hg]

This is a masterpiece! Thanks for your time and generosity to help others! You shall be rewarded, all the best

[@LambdaTest]

Much appreciated!

[@tevinjones1662]

BEST Gitlab training ever. So in depth and precise. Thank you so much!

[@LambdaTest]

Glad it was helpful! Subscribe, and look forward to more such tutorials! ✨

[@obinnaezedei856]

I just stumbled onto this channel, and so far, I think it is one of the best

[@LambdaTest]

Thank you so much for your kind words. Please subscribe to our KZbin channel for more such videos 🌟

[@supriyakhare2436]

This is the best tutorial on GITLAB concepts. Thank you Moss

[@LambdaTest]

Glad it was helpful!

[@sampathkovuri]

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!!

[@LambdaTest]

Hey Sampath 👋 Glad it helped!

[@FXMV2012]

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!

[@LambdaTest]

Thanks Frank! Great to hear

[@ewout206]

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.

[@LambdaTest]

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.

[@DevOpsEd]

This is one great and very comprehensive tutorial for Git/GitLab beginners. Excellent work Moss.

[@LambdaTest]

Glad you liked it, Please subscribe to our channel for more such tutorials.

[@avanipadaliya5609]

I love your method to teach. Anyone can easily understand. Thank you for making a video.

[@LambdaTest]

Glad it was helpful!

[@Alex-dd3oy]

Best explanation of Gitlab and git on youtube. Thank you

[@LambdaTest]

Glad you liked the video, Please subscribe to our KZbin channel for more such videos 🌟

[@aatikanazneen970]

By far the best tutorial I have seen for Git. So much clarity and intuition! Much Appreciated.

[@LambdaTest]

Glad you found this helpful😊 Subscribe to our channel to never miss an update on the upcoming tutorials! ✨

[@1306dk]

Absolutely great tutorial. Very well structured, and all concepts explained clearly with hands on examples. Thanks!

[@LambdaTest]

Glad you enjoyed it!

[@vignesh54321]

Just wanted to learn about GitLab flow and this tutorial was perfect for that. Thank you so much!

[@LambdaTest]

Glad it was helpful!

[@arishali9248]

This is a beautiful course !

[@LambdaTest]

thanks Arish

[@prolapsha]

This is just a pure gold what this MAN shared with us

[@LambdaTest]

Thanks Ilya

[@eml2948]

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

[@LambdaTest]

Thanks EML, Glad you liked it

[@jasonhe6947]

Really appreciate your video. You explain things so well, really thankful for that.

[@LambdaTest]

Glad it was helpful!

[@yecineabdelhedi1358]

Many thanks for this tutorial Moss. That was really helpful. Good Job!

[@LambdaTest]

Hey Yecine👋 Glad you enjoyed it!

[@shashankmarri1056]

Very good video, all the basics have been covered very well.

[@LambdaTest]

Glad it was helpful!

[@alkalinebase]

Truly, Thankyou so much. Videos like these are a gem when you are on your self taught journey!

[@LambdaTest]

So glad you liked it !

[@jannavratil1306]

Great explanation ! :)

[@LambdaTest]

thanks Jan!

[@sharazhaider255]

Amazingly explained

[@LambdaTest]

Glad it was helpful!

[@abdullahbasaad3463]

Amazing and simple demonstration. Every single part is explained perfectly. Go ahead, well done.

[@LambdaTest]

Glad it was helpful!

[@kuo-liangchang8065]

Thank you so much, I have learned so much for watching this video!!

[@LambdaTest]

Thanks Kuo-Liang Chang. Glad it was helpful

[@mtf8_music]

alias virtue_signal="git config --global init.defaultBranch main"

[@manuchaudhary7902]

Just started the course. Really looks like a great course.

[@VenuGopalReddy.]

Wow, it was very clearly explained and got to know many things about hitlab...Thanks for sharing!!

[@LambdaTest]

Glad it was helpful 💖

[@nimalansuntharamoorthy765]

Its a master piece. All got well explained..

[@LambdaTest]

Thanks Nimalan, Glad it was helpful

[@sasukeshinobi1691]

WHAT IS THIS ?!!!! U ARE AWESOME DUDE

[@LambdaTest]

Thanks 😊 Subscribe to our channel to never miss an update on the upcoming tutorials! ✨

[@mahmoudmahany3489]

This video is a life saver. Thanks for the efforts :)

[@LambdaTest]

Glad it helped!

[@Bathi666]

This is amazing mate. Thank you!

[@LambdaTest]

Glad you liked it! Subscribe, and look forward to more such tutorials! ✨

[@Bathi666]

@@LambdaTest already done. Really appreciate it

[@ozeangorgon]

Marking where I left off: 1:27:08

[@player95]

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.

[@LambdaTest]

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.

[@alute2589]

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

[@LambdaTest]

Hey there 👋🏻 Glad you liked it. Thanks for the suggestion. Stay tuned⚡

[@ChandanKumar-pk5kh]

Bro.. you are the best of the best

[@LambdaTest]

Thanks Chandan

[@Mohammed-co3ux]

The best video for Gitlab in the entire KZbin 😅

[@LambdaTest]

We're delighted that you found it helpful! 😊 Don't forget to subscribe to our channel for the latest updates on upcoming tutorials! ✨

[@bog9867]

Thanks for simplifying Git and GitLab, well explained.

[@LambdaTest]

Glad it was helpful!

[@Ghost-zi2eo]

can u pls explain how to override variables in application.properties or just use gitlab variables in maven project

[@LambdaTest]

You can try setting the Environment Variables in your Project -> Settings -> CI/CD -> Environment Variables and also in the .gitlab-ci.yml file

[@RecordToDeathToBoredom]

12:06 what did you do after typing "hello!"? I'm stuck at this part.

[@LambdaTest]

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.

[@sushantdhakal3117]

liked and subscribed. hope your channel grows brother

[@LambdaTest]

Thanks for the sub!

[@TheShmooty]

Thanks mate, appreciate the work you put in to create these

[@LambdaTest]

Glad you like them!

[@PATTY9XY]

Thanks for uploading this.I will follow your videos to learn more about gitlab.

[@LambdaTest]

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! ✨

[@Alezi8]

Thank you very much unique and excellent presentation!!!

[@LambdaTest]

Glad you liked it! Do subscribe the channel for more such tutorials!🙂

[@andersmadsen4487]

Which terminal are you using? I don't get any hints in the windows command prompt nor in Bash :/

[@LambdaTest]

Hey there, If you're looking for hints or autocomplete features in a terminal environment, here are a few suggestions that might enhance your experience in both Windows and Bash (Linux/Unix or macOS environments): Bash Completion: Ensure you have bash-completion installed and enabled. Many distributions come with it pre-installed, but you might need to enable it by adding scripts to your .bashrc or .bash_profile. Bash completion enhances the autocomplete features, offering suggestions for commands, file paths, and more. Oh My Zsh: If you're open to using a different shell, consider switching to Zsh with Oh My Zsh. It's highly customizable and offers powerful features like advanced autocomplete, themes, and plugins that can significantly improve your terminal experience. Fish Shell: Another alternative is the Fish shell, known for its excellent autocomplete and suggestions. It provides suggestions as you type, based on your history and the file system, making it easier to work without memorizing complex commands.

[@andersmadsen4487]

Thanks a lot for the answer ^_^ I went through a lot of trouble to try to get Fish to work. Bash found neither of the commands "sudo" nor "apt", which the internet suggested I used to get Fish, but also to get eachother. So that sucks. So I installed Ubuntu with/on WSL and at first didn't get that to install Fish either, but then suddenly it worked anyway somehow. But it is super unstable/slow and simple commands like "ls" doesn't work. So I think I'll remove Ubuntu and Fish again and just move on with Bash, which I did get to autocomplete upon tab. Also: (same as the other guys) really great tutorial! Thank you! ^_^ @@LambdaTest

[@LambdaTest]

Hey there, First of all thank you for your kind words, I'm sorry to hear about the difficulties you've experienced trying to set up Fish on your system. Transitioning to different shells or environments can indeed present some challenges, especially with varying levels of support and stability. Here are a few thoughts and tips that might help with similar situations in the future or provide some context: Command Not Found Issues: If you're encountering issues where basic commands like sudo and apt are not found, it's possible you're on a system that doesn't use apt as its package manager (for example, macOS or certain Linux distributions). Alternatively, if you're in an environment like Windows Subsystem for Linux (WSL) but are experiencing these issues, it might indicate a problem with the WSL setup or the specific Linux distribution's configuration. WSL Stability and Performance: WSL should generally offer good stability and performance, but experiences can vary based on your Windows version, WSL configuration, and the specific Linux distribution you're using. WSL 2, for instance, provides significant improvements over WSL 1 in terms of file system performance and Linux compatibility. If you're experiencing slowness or instability, ensuring you're on WSL 2 and checking for any available updates to Windows and WSL might help. Fish Shell Installation Troubles: Fish is known for its user-friendly features, like advanced autocomplete and a rich scripting environment. However, installing it can be tricky if the environment isn't set up correctly or if there are compatibility issues. Using Ubuntu on WSL is generally a good choice for compatibility with most software, including Fish. If installation issues arise, checking the official Fish documentation or community forums can provide specific guidance and troubleshooting steps. If you decide to try switching shells or environments again in the future, consider looking into more detailed guides or community support for the specific tools or systems you're working with. Sometimes, a fresh installation or a different approach to troubleshooting can resolve unexpected issues.

[@andersmadsen4487]

Thank you so much ❤ Your help is much appreciated! @@LambdaTest

[@Tabrez_Akhtar]

Really an excellent resource to go through for gitlab.. Thank you #LambdaTest

[@LambdaTest]

Glad you liked this😊 Subscribe to our channel to never miss an update on the upcoming tutorials! ✨

[@lnpangel9785]

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.

[@LambdaTest]

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!

[@praveen_rahul7117]

Thank You For this Awesome Tutorials , Really helpfull !.

[@LambdaTest]

Glad you like them!

[@ravshanbekortikov1805]

this is a good one!🙌

[@LambdaTest]

Glad you liked it! Subscribe to our KZbin channel to get more tutorials videos.

[@techdude_bb]

Thanks for making this video, really good and helpful!

[@LambdaTest]

Hey Bryan 👋 Glad it was helpful!

[@shahedulislam94]

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.

[@LambdaTest]

Hi Shahe, Let us get back to you

[@LambdaTest]

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

[@cradical2808]

This was exactly what i needed

[@LambdaTest]

Thanks Cradical!

[@durgeshkshirsagar5160]

Excellent tutorial! Thank you for your efforts and such a nice video!

[@LambdaTest]

Glad it was helpful! 💖

[@absharma534]

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.

[@LambdaTest]

Glad you liked the video! Thanks for the suggestion, and look forward to more insightful videos! 🙌

[@Rock43055]

great video, thx!

[@BenOuiEtAlors]

Thank you very much! I like this step by step tutorial!

[@LambdaTest]

Glad you liked it 😊 Subscribe to our channel for more such tutorials! ✨

[@WildGrowthJ]

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?

[@LambdaTest]

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.

[@WildGrowthJ]

Wow that’s awesome! Thanks so much!

[@crywalt]

Thrilled to see someone using vim.

[@LambdaTest]

High five 🖐🏻

[@dimakatout131]

Adorable Tutorial . Thank you for sharing this

[@LambdaTest]

Glad you liked it! Do subscribe the channel for more such video tutorials

[@mehdizineddine5402]

thank you for the cours , but i have an issue with that , you depend on Maven 5 min and in some cases it doesn't work so how we suppose to follow the next of this sours !!

[@LambdaTest]

Hey @mehdizineddine5402 , Thanks for your feedback! I recommend double-checking your Maven setup or trying a different version. If the issue persists, feel free to reach out for more detailed support.

[@Gp-ez6ji]

Thank you so much for the basic git section of the video!

[@LambdaTest]

Glad it was helpful! 🙂

[@rajkiransenapaty]

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.

[@LambdaTest]

Hey Rajkiran, You can check out the steps of configuration on this blog docs.gitlab.com/ee/user/project/integrations/pipeline_status_emails.html

[@jou3883]

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?

[@LambdaTest]

Hi Aznim, Let us get back to you on the same

[@guswind4636]

Excellent!! thanks for sharing this tutorial

[@LambdaTest]

Glad it was helpful!

[@Ezad99]

I'll be honest got a bit lost at the CI/CD section, anyone got any recommendation on how I can learn that better

[@teodorgeorgievbg]

By the way, for switching to a branch, you should use the "new" switch command, instead of "checkout"

[@LambdaTest]

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.

[@GM-qv1ql]

Nice video. Great job!

[@LambdaTest]

Hey there, Thanks for your kind words😇 Make sure you subscribe to our KZbin channel for more 👋🏻

[@ashvinla]

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

[@LambdaTest]

Hi Ashvin, Glad to hear that. For your question, let us get back to you

[@ashvinla]

@@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.

[@LambdaTest]

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

[@yinebebtariku1617]

partially great tutorial - good job

[@LambdaTest]

Many thanks!

[@ReminiscewithJohn]

Subscribed, so clear and precise.

[@LambdaTest]

Glad you liked it! ✨

[@sksafikuddinkhan5935]

There's protected environment, approver has been added as well, but when a approver approve or reject the pipeline with some comment, where to see that comment? I checked under pipeline, it's not visible, only showing, that it has been rejected/approved. Please help me how and where to see the comments.

[@LambdaTest]

Hi Safikuddin, When you use protected environments with approvers, the comments left by the approvers are typically visible in the merge request associated with the pipeline rather than directly in the pipeline view itself.

[@dannybuntu]

At 7:00 I did: git branch -m main error: refname refs/heads/master not found fatal: Branch rename failed

[@LambdaTest]

Hi Daniel, let us get back to you on this

[@synntroll5]

@@LambdaTest Is there a solution? I got the same error

[@LambdaTest]

Hi Daniel, This error occurs because GitHub has changed the default branch from master to main. To fix this follow the following ways: 1. git remote add origin [e-mail]: 2. git add . 3. git commit -m "first commit" 4. git branch -M main 5. git push -u origin main Ref: www.henryxi.com/git-refname-refs-heads-master-not-found

[@LambdaTest]

This error occurs because GitHub has changed the default branch from master to main. To fix this follow the following ways: 1. git remote add origin [e-mail]: 2. git add . 3. git commit -m "first commit" 4. git branch -M main 5. git push -u origin main Ref: www.henryxi.com/git-refname-refs-heads-master-not-found

[@wasim289]

Hi MOS, I have one strong doubt, using cicd pipeline on which application server our artifact is getting deployed?

[@LambdaTest]

Hi Wasim, let us get back to you

[@LambdaTest]

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 :)

[@dudhaniss]

Great tutorial!

[@LambdaTest]

Glad you liked it 😇 Make sure you subscribe to our KZbin channel for more 👋🏻

[@anotherjuli]

Amazing work and dedication!

[@LambdaTest]

Glad you liked this😊 Subscribe to our channel to never miss an update on the upcoming tutorials! ✨

[@suaibislam2923]

Hi Moss. Getting error on executing "git branch -m main". "error: refname refs/heads/master not found fatal: Branch rename failed".

[@LambdaTest]

Hey Suaib, let us get back to you on this

[@LambdaTest]

Hi Suaib, This error occurs because Github has changed the default branch from master to main. To fix this follow the following ways: 1. git remote add origin [e-mail]: 2. git add. 3. git commit -m "first commit" 4. git branch -M main 5. git push -u origin main Ref: www.henryxi.com/git-refname-refs-heads-master-not-found

[@mallikarjunsoma5232]

Very well explained. Thank you for this wonderful tutorial.

[@LambdaTest]

You're very welcome! Glad it was helpful! 😇

[@krzysztofdowgird616]

very good quality:)

[@LambdaTest]

Glad you think so!

[@krzysztofdowgird616]

@@LambdaTest greetings from Poland:)

[@muddassirahmad36]

Just one word RESPECT

[@LambdaTest]

Thanks Muddassir, Glad you liked it 💖

[@kisahulyafamily520]

Well done bro...thanks a lot

[@LambdaTest]

Thanks and welcome

[@jorgen180]

Great tutorial! Very well explained!

[@LambdaTest]

Thanks for the feedback! 🙌

[@cabc2011]

5 Stars, Thanks Moss

[@LambdaTest]

Glad you liked it! Please subscribe to our KZbin channel for more such videos 🌟

[@aladin5985]

Great Initiative

[@LambdaTest]

Thanks AlaDin

[@vedanti-vidhan4766]

this is really an amazing tutorial

[@LambdaTest]

Glad you liked it! Please subscribe to our KZbin channel for more such videos 🌟

[@artemkeller2571]

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?

[@LambdaTest]

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 [e-mail]

[@randyweems2531]

great stuff man

[@LambdaTest]

Thanks Randy

[@tetakamgasteve5876]

salut a vous je savoir comment accéder a un groupe de travail sur Gitlap

[@LambdaTest]

Hi Teta, Can you help us translating your question in English? :)

[@miguelv2985]

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?

[@LambdaTest]

Hey miguelv, let us get back to you on this

[@LambdaTest]

Miguelv, Please try setting the maven path variables on job level rather than the pipeline

[@miguelv2985]

@@LambdaTest Thank you. I'll give that a try.

[@joergheilig]

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

[@bestmeetupdestinations-del4642]

nice,can we use this project for poc?

[@LambdaTest]

Hey there 👋🏻 Please let us know if we can help in anyway ⭐️

[@ComputationalArt]

Thanks !! It's very useful !!!

[@LambdaTest]

Glad you liked it! Subscribe, and look forward to more such tutorials! ✨

[@ferhatgul4338]

very very fruitful, thanks.

[@LambdaTest]

You are most welcome

[@hamzanaseer1529]

Clear and concice. Thanks alot

[@LambdaTest]

Glad it was helpful!

[@uidevart]

Your videos are awesome :) Thank you

[@LambdaTest]

Glad you like them! 👋