Most of what I write is on TheServerSide.
If you want version control without the command line angst this guide will show you how to use Git and GitHub Desktop like a civilized human. We will cover installing the tools configuring your identity creating or cloning a repository making commits branching pushing code and opening pull requests. Yes you will learn the parts that actually matter and I will make a few sarcastic asides along the way.
Start by downloading Git for your operating system and then install GitHub Desktop. Git provides the engine under the hood and GitHub Desktop gives you a friendly GUI to do the common tasks faster. If you love the terminal you can keep using it and nothing will explode. If you do not love the terminal you will still get to look like you know what you are doing.
Tell Git who you are so your commits do not show up as the mysterious anonymous human. Run these commands in a terminal or paste them into your preferred shell.
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
GitHub Desktop also has settings for theme and default branch if you want to click rather than type. Make sure your email matches the address on your GitHub account if you want contributions to link back to your profile.
Open GitHub Desktop and choose New Repository to start local work or choose Clone Repository to copy a remote project to your machine. The app will show untracked files and the repository tree so you can see what is going on without incantations.
Edit files in your favorite editor. When you are ready return to GitHub Desktop and stage selected files. Add a commit message that explains why you made the change not just what you changed. Good commit messages are a gift to your future self and everyone else who inherits your code.
git add .
git commit -m "Fix user input validation and add tests"
If you prefer the GUI click the checkboxes for the files add a clear message and hit Commit to master or to whatever branch you are on.
Click Push origin in GitHub Desktop to send local commits to GitHub. For new work create a branch for a feature or fix and switch between branches from the branch menu. Branching keeps the main branch clean and production ready which is nice for everyone except chaos.
After you push a branch open a pull request on GitHub to request review and run any automated checks. Once approved use the merge button to combine the work into main then pull the updated main branch back to your machine. If there are conflicts resolve them locally or with the web editor and commit the result.
If you see merge conflicts do not panic. Open the conflicting files resolve the differences commit the result and push the branch again. If history feels messy consider an interactive rebase from the command line to clean it up before pushing. Remember the GUI will not hide bugs but it will make you feel better while you hunt them down.
Use clear commit messages branch for features and use pull requests for review. Keep your local and remote branches in sync and delete feature branches after merging to avoid digital clutter. With GitHub Desktop you get an approachable workflow for daily version control tasks and with Git you keep the power when you need it. Now go commit something useful and do not forget to give your commits names that future you will not curse.
I know how you can get Azure Certified, Google Cloud Certified and AWS Certified. It's a cool certification exam simulator site called certificationexams.pro. Check it out, and tell them Cameron sent ya!
This is a dedicated watch page for a single video.