Skip to main content

Git and GitHub Version Control Experiment

Title: Git and GitHub Version Control Experiment

Objective:

The objective of this experiment is to demonstrate the basics of version control using Git and GitHub. We will create a simple repository, make changes to files, commit those changes, and push them to a remote GitHub repository.

Prerequisites:

  • Git installed on your local machine. You can download it from https://git-scm.com/downloads.
  • A GitHub account. You can sign up for free at https://github.com.

Experiment Steps:

Step 1: Set up Git Configuration

Open a terminal or command prompt and run the following commands to configure your Git identity:
       git config --global user.name "Your Name"
       git config --global user.email "youremail@example.com"

Step 2: Create a Local Git Repository

  1. Create a new directory on your local machine for the project.
  2. Navigate to the project directory using the terminal.
  3. Initialize a new Git repository:

       git init

Step 3: Create a Sample File

  1. Create a simple text file called sample.txt in the project directory with some content.

Step 4: Add and Commit the File

  1. Add the file to the staging area:

        git add sample.txt

  • Commit the changes with a meaningful message:

        git commit -m "Add sample.txt file"

Step 5: Create a GitHub Repository

  1. Go to https://github.com and log in to your GitHub account.
  2. Click on the "+" icon in the top right corner and select "New repository."
  3. Give your repository a name and optional description, then click "Create repository."

Step 6: Link Local Repository to GitHub Repository

  1. In the terminal, add the remote URL of the GitHub repository to your local repository:

        git remote add origin <GitHub_Repository_URL>

Step 7: Push Changes to GitHub

  1. Push the committed changes to the remote GitHub repository:

        git push -u origin master

Step 8: Make Changes and Push Again

  1. Edit the sample.txt file and add some new content.
  2. Save the changes and commit them:

        git add sample.txt

        git commit -m "Update sample.txt file"

  • Push the changes to the GitHub repository:

        git push

Step 9: Check GitHub Repository

  1. Open your GitHub repository in the browser and verify that the changes you made locally are reflected in the repository on GitHub.

Conclusion:

In this experiment, you learned the basic workflow of using Git and GitHub for version control. You created a local Git repository, added and committed files, linked it to a remote GitHub repository, and pushed changes to GitHub. This simple example demonstrates the power and convenience of version control in collaborative software development.

Comments

Post a Comment

Popular posts from this blog

Maven Create and Build Artifacts

In Maven, you can create and build artifacts using the package phase of the build lifecycle. The package phase is responsible for taking the compiled code and other project resources and packaging them into a distributable format, such as a JAR (Java Archive), WAR (Web Application Archive), or other custom formats. Here are the steps to create and build artifacts using Maven: Configure the Build Output: In your project's pom.xml file, you need to configure the output of the build. This includes specifying the type of artifact you want to create (e.g., JAR, WAR) and any additional resources to include. You do this in the <build> section of your pom.xml: <build>     <finalName>my-artifact</finalName> <!-- Name of the artifact without the extension -->     <plugins>         <!-- Plugin configurations for creating the artifact -->         <!-- For example, maven-jar-plugin or maven-war-plugin -->     </plugins> </build> Depend
Post a Comment
Read more

Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server

  Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server  Objective: The objective of this experiment is to set up a CI/CD pipeline for a web development project using Jenkins, Git, and webhooks, without the need for a Jenkinsfile. You will learn how to automatically build and deploy a web application to a local HTTP server whenever changes are pushed to the Git repository, using Jenkins' "Execute Shell" build step. Introduction: Continuous Integration and Continuous Deployment (CI/CD) is a critical practice in modern software development, allowing teams to automate the building, testing, and deployment of applications. This process ensures that software updates are consistently and reliably delivered to end-users, leading to improved development efficiency and product quality. In this context, this introduction sets the stage for an exploration of how to apply CI/CD principles specifically to web development using J
1 comment
Read more

Maven Repositories (local, central, global)

Maven relies on repositories to manage dependencies, plugins, and other artifacts required for a project. There are typically three types of repositories in Maven: local, central, and remote/global repositories. Local Repository: Location: The local repository is located on your local development machine. By default, it's in the .m2 directory within your user home directory (e.g., C:\Users\<username>\.m2\repository on Windows or /Users/<username>/.m2/repository on macOS and Linux). Purpose: The local repository is used to store artifacts (JARs, POMs, and other files) that your machine has downloaded or built during previous Maven builds. These artifacts are specific to your local development environment. Benefits: Using a local repository improves build performance since it caches dependencies locally, reducing the need to download them repeatedly. It also ensures reproducibility by maintaining a local copy of dependencies. Central Repository: Location: The central repo
Post a Comment
Read more