Navigating GitHub: From Production to Open-Source Contributions
GitHub stands as a cornerstone in the realm of technology, fostering collaboration, innovation, and boundless creativity. In this blog, we’ll dive into the depths of GitHub’s ecosystem, uncovering its myriad features and showcasing its transformative impact on the tech landscape.
The journey start from writing a code i.e. Hello World (obviously this is first line of code of every coder). To start with Git, install Git bash. In GitHub there are two environments i.e. Production environment, Developer environment.
First developer writes the code and then deploys the code. Deployment just means to run the code on server that is available to everyone or user. So, the process is started from writing a code from local to the production. Running the code in local is called Developer environment. And Production environment is where the users can do the things.
Production means code is getting deployed to one server, that is code is available to everyone. And we want everyone to access that website, so we run this website on a server and this server has an IP called public IP. And this IP has a domain i.e. DNS (Domain Name System) domain and user hit this domain to access the website. Domain can be google.com.
Workstation:
It is a device where we write the code i.e. our laptop.
Workspace:
The thing where we are saving the code, like the folder.
Version Control System: Keeping Track of Project Evolution
Imagine you’re working on a big group project, like building a Lego castle with friends. Everyone has their own ideas for the castle design, and you all want to add your own pieces and make changes. But what if someone accidentally removes a crucial part, or you want to go back to an earlier design?
A version control system (VCS) is like having a magic Lego box that keeps track of every change made to the castle. It remembers who added what, when they added it, and even allows you to go back in time to any earlier version of the castle.
So, if something breaks or if you want to see how the castle looked two days ago, the version control system saves the day! It helps teams work together on projects, keeps everything organized, and lets you travel back and forth in time to see how your project evolved.
There are many tools that offer version control system but Git is widely used. And Git has more features. There are many big companies as well, they don’t use Git but create an own version control system.
Navigating Challenges: Merge Conflicts and Collaboration
When two developers write code on same issue and both the code are correct. Then which code should be merge is the merge conflict. In this scenario, we see which is more effective code and merge that code. Or we can merge both the codes.
Readme: Understanding Version Control Systems in Plain Language
We have our code but for other person, to know what is dependency and how to run this project and what is this project all about, for this purpose we create a documentary known as readme.
Enjoy Learning! 😊
You can connect me on Linkedin: https://www.linkedin.com/in/palprerna/
