Article
How to Register and Use SmileVoice
Complete guide to setting up and using SmileVoice for affordable VOIP calls over 4G LTE.
Read Article
Article
Article
Setting Up Your IT Infrastructure
A comprehensive guide to building a solid IT foundation for your business, from networks to security.
Read Article
Article
Git Branching Without Affecting Master
Learn how to use Git branches to implement new features safely without breaking your main codebase.
Read Article
Video
Setting Up Your IT Infrastructure
Video walkthrough of essential IT infrastructure setup for small and medium businesses.
Watch Video
Guide
Git Command Cheat Sheet
Quick reference guide with all essential Git commands for everyday development workflows.
Download PDF
External
Microsoft Azure Documentation
Official Azure documentation for cloud services, virtual machines, and enterprise solutions.
Visit Site
External
AWS Getting Started Guide
Comprehensive guide to getting started with Amazon Web Services for cloud computing.
Visit Site
Featured Tutorial
Git Branching Best Practices
What is Git Branching?
A Git branch is the fundamental means of launching a separate line of development within a software project. It allows development to continue in multiple directions simultaneously and potentially, to produce different versions of the project.
The default branch in a repository is named master (or main) and most developers keep the repository's most robust and dependable line of development on that branch.
When Should You Use a Branch?
$ git branch
A branch is suitable for continuing development. It is dynamic and moves with each commit you make.
- Use a branch to represent individual customer releases (e.g., version 1.0 vs 1.1)
- Encapsulate development phases: prototype, beta, stable, or bleeding-edge
- Isolate development of a single feature or complex bug fix
- Facilitate merging of several branches prior to release
Creating a New Branch
$ git checkout -b new-feature
Naming your branches is up to you and your project policies. Consider whether the naming convention will be static and immutable, or dynamic for development.
Merging Your Branches
$ git merge new-feature
After creating a branch and completing your work, you'll need to merge it back to the master branch when ready.
Best Practices
- Always create a new branch before developing a new feature
- Restrict direct merging to the master branch
- Sync local master branch only from upstream to local
- Push to origin master branch only from local to origin
- Rebase master branch onto your feature branch periodically
Need Help With Your IT Projects?
Our team of experts is ready to help you implement the right technology solutions for your business.