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.
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.
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.
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!
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!!
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
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
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.
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.
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.
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.
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 !!
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.
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.
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.
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 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
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!
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.
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.
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.
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?
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.
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
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.
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.
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
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
Thank you for taking the time to share your feedback. We're sorry to hear that you found the material unengaging. We always strive to improve and provide content that is both informative and engaging. Your feedback is valuable, and we will take it into consideration for future content. If you have any specific suggestions on how we can make the material more engaging, we would love to hear them. Thank you again for your feedback!
