- 10
- 187 102
Ako Dev
United States
Приєднався 21 чер 2020
How to Fix Case Mismatch Issues in Git | Git File Rename Problem Solved!
Running into issues with Git when renaming files due to case sensitivity? Learn a quick and effective solution to resolve case mismatch problems when renaming files like 'FreeTest.js.js' to 'freeTest.js'. This step-by-step guide will help you avoid common pitfalls in Git and ensure your repository stays error-free. Perfect for developers facing file naming conflicts on case-insensitive file systems. Subscribe for more Git tips and tricks!
Переглядів: 189
Відео
Unlocking the Tech Interview: Real-time Reviews with Industry Experts!
Переглядів 58Рік тому
Dive into "Cracking the Code Interview" - our exclusive series aimed at demystifying developer interviews. 🎥👩💻 Join us, seasoned developers from Hard Rock Sportsbook, Prudential, and more, as we conduct live mock interviews and provide invaluable insights. Whether you're prepping for an interview or looking to understand the dos and don'ts, this series is tailor-made for you. Bonus: If you're ...
5 MUST HAVE Books for Coders: Boost Your Skills & Teamwork! | Part 1
Переглядів 90Рік тому
Dive into the world of software development with my top 5 book recommendations that every developer should own! Whether you're starting out or looking to refine your practices, these reads are crucial for individual growth and mastering team collaboration: 📘 "Clean Code" by Robert C. Martin Learn the art of writing clear and modular code. Elevate your skills and ensure your code is a joy for ot...
Is Coding for Everyone?
Переглядів 3293 роки тому
In the past couple of years multiple bootcamps have opened promising the sky, but is coding for everyone? what should we look for in ourselves before we sign up? Let me help you pose some of these questions to make the best decision. Take a look at a book called CodeComplete and it's series. If you want to prepare yourself this is a book everybody should read! amzn.to/3qE0iDd If you didn't get ...
Git for Teams: Streamlining the Fetch, Pull, and Merge Process
Переглядів 8 тис.3 роки тому
🔍 Description: Dive deep into the essential Git commands every developer should know! This comprehensive tutorial will guide you through the intricacies of git fetch, git pull, and git merge when collaborating in a team setting. Building on the success of our top-performing video "How to use git when working within a team", this guide will further enhance your team collaboration skills using Gi...
Trapped in Vim? 🚫 The ONE Trick to Escape Every Time!
Переглядів 3503 роки тому
Stuck in Vim and can't find your way out? This tutorial is your guide to confidently exiting Vim every time. Dive in as we explore the most common stumbling blocks and offer clear solutions to navigate the renowned text editor. From mastering the exit command to understanding Vim's unique interface, we've got you covered. Whether you're a beginner or just need a refresher, this video will help ...
How to use GIT when working with a team?
Переглядів 178 тис.4 роки тому
Hi all welcome to ako.dev! So you know git... now how do you use it when you work with a team for work or on a project? do you just use the same branch? Lets try and put a workflow together so it makes our lives easier! Take a look at a book called Code Complete and its series! If you want to prepare yourself for real scenarios this is a book everybody should read! amzn.to/3qE0iDd
Clone Your DEV Environment For Your Team within SECONDS! 😲 The Ultimate Team Trick
Переглядів 1724 роки тому
Want to set up your entire developer environment on a new computer with just one click? Discover our game-changing method to sync EVERYTHING using Dropbox. Dive in to learn the secret trick professionals don't want you to know. Master this and enjoy a hassle-free developer life across all your devices!
Node & React: Ultimate Setup Guide!
Переглядів 1544 роки тому
Unlock the power of modern web development with this comprehensive guide on setting up a Node.js and ReactJS project from scratch. Whether you're a beginner looking for a solid start or an expert wanting a refresh, this tutorial ensures your foundation is rock-solid. Dive in now to supercharge your web apps! 🔥 #NodeJS #ReactJS #WebDevelopment #SetupGuide
Here's a scenario: Time 1: A created a feature branch based on master. Time 2: A worked on 1 commit on the feature branch. Time 3: There is a new commit (maybe a merge) in the master branch. Time 4: The next day, A wants to continue to work on the feature branch. Question: Should he do a git pull in the morning before doing his work? Also, after the pull, how should he incorporate the changes in master into his feature branch? Or should he? Lastly, if the changes in master totally removed some main functions where his feature branch is based on, what should he do? Thank you!!
Yes, when you come in, you should always do a pull into your feature branch, this will make it easier when merging back into main/master to clarify the direction of the merge should be from Master/main --> yourFeatureBranch one more question to help, the only way that they can delete something you are working on, is if you merge your branch into main, but once thats done, why are you continuing with the feature branch?
Constantly pull from master ? Or branch we create day by day?
Pull from master to keep your branch up to date
Loving it , Thanks man!
Glad to hear it!
I was curious about the private repo, how I will add contributors, and how to put limited access, such as branches, so they could not push changes to the repo as origin main or master.?? Thank you very much!!!
ill make a video about this, probably a short. give me a week from the date of this comment
helped much! Thank you!!
So helpful for us noobs man, thank you for making this
This is the best! Can you tell us more what happens if you find sth wrong after pushing to origin
what is the -A parameter used for? Looks like an "all" but git add already does that so it's why i'm asking.
you are right, and this is mroe a habit, nowadays git add defaults behind the scene to git add -A. here is what the official documentation says: ``` -A --all If no <pathspec> is given when -A option is used, all files in the entire working tree are updated (old versions of Git used to limit the update to the current directory and its subdirectories). ```
Wonderfull
Love the point about asking your interviewer, how the company handles sprints ?. it's a great way to analyze if the role will be a great fit for you
Agreed! It’s important to know what you want in a position and making sure you ask the right questions to get the best understanding of the role you’re applying for!
hey, how'd you get your terminal to look like that?
I have the cobalt theme, and im using iterm2 with oh-my-zsh.
Thank you so much for the video! This has helped me tremendoulsy at my first job! Also the book Code Complete that you suggested in the video description is a winner! A big big big reason why i was able to get past some of my tech interviews while applying to jobs. If you haven't read code complete i highly suggest checking it out. Link in bio!!
Thrilled to hear the video made a difference for you! "Code Complete" is indeed a gem. Always happy to share resources that can uplift the community. Keep pushing forward!
I like how you get to the point with this video. Great examples showing a successful merge and resolving a conflict. When you are on a tix-5 branch, does that the tix-5 branch show up on your local file directory? I see you can confirm which branch you are on in the terminal, but I am curious if you can visualize it when you're working on local? thank you.
Use VS code ..to visualize on locally
if you want to see local branches ' git branch ' and if you want to see the remote branches (those on your github) then do ' git branch -r ' let me know if that helps
Thanks a lot. Very useful and straightforward 🙌🙌
You're welcome!
Amazing...
Appreciate it! Anything I can do!
Thank you so much. Very informative video.
Anything I can do to help! Please let me know if there are other topics you’d like to hear about!
Thanks for this video, I learn a lot from this!
Of course! Let me know if there’s any other topics you’d want to hear!
HELP
Is there something I can do to help?
Awesome video, I had so much trouble resolving merge conflicts before. Is there a certain extension needed in VScode to get those accept changes options?
nope, it should just come up, you can always try to restart vscode if it doesnt pick it up.
Thank you very much!
Thanks a lot!
Please, can anyone help When you clone repository - did you do it on the companies repository or we should fork, and clone from the copy of our account?
sorry for the delayed response, but you dont need to fork it, you should be able to clone the repo locally.
Awesome Explanation. Very Straight forward. Can you clarify my doubt. I am new to git. In your video when you pushed new branch to remote. Branch created in Origin with All Files, in that Branch we see all files instead of just Committed files. You committed only one file right .. But we see 2 files in that newly created branch. In My Project I have 100's of files For every small change if i push that branch, All files will be pushed. Can i Create New Branch with Only Committed files ? Thank You
Hey Prakash, when you create a new branch, you are making a temporary copy, when making changes only those changes will be pushed, no need to be pushing 1000's of files. thats why git is so cool, because it only updates the files where changes have been made. I would probably check if your .git, is not outside of the original repo folder.
Does pushing local branch to github automatically creates pull request( merging the branch to master branch) ?
no it does not, on github it shows a suggestion, but its not automatic (can you make it automatic, we can make a video how to do that)
Well explained! I was struggling trying to understand how to do certain functionality prior to watching this and now my questions have been answered. Thank you!
Anything I can do! This was something I struggled with early on as well. Let me know any topics you’d like to hear!
Extremely helpful! Thanks!
Glad it helped!
Just what I needed, legend
same
This was a great video for me to document the git process for my team, thanks!
A lot of tutorials on youtube regarding this but you my friend have made it simple and without the 'fluff' - straight to the point and with a simple practical example.
Simple and clear explanation!
shoutout to all the oldschool coders that did not abandon SVN for git
Thank u, u saved my life bro!
Happy to help
when i did a git fetch -all....i didnt get the list of branches what actual it is
That's an awesome practical tutorial.. Thanks
Glad it was helpful!
why "pull origin master" when you are about to delete the branch?
this is so it does not cause merge conflicts with master
Great simple video, helped me a lot, thank you!
that was good
Thanks man
but shouldnt the pull origin master be before pushing the feature branch?
Great video! Super clear and to the point! A lot of other tutorials dont cover the team working workflow but this is gold! What about using more branches like release and hotfix? Are there good examples how to use those? Greetings from germany 🙂
much appreciated brother
Question: what is the point of delete the older ticket branch if it doesnt remove the branch on github?
People like to see what branches they actually are working on, so instead of having a lot of dead branches, it cleans it up and is easier to see where you are or what you have outstanding
@@williamavasquez If they leave those branches on the remote, doesn't that mean the next time you pull from that repo, those branches will get created again locally?
Thanks a lot , u have saved a lot of hours for me
One of the best explanation 👌
Thank you so much. You’ve answered all my questions on collaborations.
Greattt Video was very helpful
Thank you.
Thank you so much for this... I was confused watching a lot of other tutorials but this cleared my doubts
one of the best shortest practical video explanation on github. I have seen many videos they are only theory and even some of them are not showing practical but u r video is just like begginer of the github can even understand it tq very much
Question abt creating the pull request at 5:28. Is the assumption here that all team members have access to this github account, hence can create the pull request from within the account UI?
Anyone can make a pull request, as long they have read access (not private repo)