Future Something

Hi 👋, I'm a second year college student at Mapúa Malayan Colleges Laguna, currently pursuing a degree in Bachelor of Science in Information Technology. I am interested in Web Design and hopefully become a front-end developer in the future someday.

• 🚴‍♂️ My hobbies include: cycling, editing and graphic design.

• ⚡ I am currently interested in learning more about Web Development and Design.

• 🏝 I love the City Pop Aesthetic. I follow the works made by Hiroshi Nagai, Eizen Suzuki, Ardhira Putra, and Tree_13.

• 🎵 I currently like listening to the Math Rock genre.

This cheat sheet provides a quick reference to Git commands I use. The examples I provided may be different as I use a MacOS machine and run these commands using a Bash terminal.

1. git init - This is the very first step to start tracking changes in your project. It initializes a new and empty Git repository in your local repository. It has no parameters, but it is needed to specify which directory to initialize a Git repository first before running git init.

   Example:

   $ cd ~/Repositories/my-awesome-project
   $ git init

2. git clone [url] - If you want to work on an existing remote repository that has Git initialized, use git clone. This command downloads a remote repository to your local machine. Its parameter needs you to provide the URL of the repository you want to clone, and like git init, it is also important to specify which directory you want Git to download the project.

   Example:

   $ cd ~/Repositories
   $ git clone https://github.com/jp-gerona/jp-gerona.git

3. git add [file] - After making changes to your files, you need to tell Git which changes you want to track or stage. Use git add [file] to add specific files or simply git add . to add all modified files in the local repository to the staging area.

   Example:

   $ git add .

4. git commit -m "[description]" - Once you've added the desired changes to the staging area, use git commit to take a snapshot of those changes and store them in the Git history of your local repository. It is good practice to always provide a clear and concise message describing the changes you've made using the -m flag.

   Example:

   $ git commit -m "Added a new super awesome feature"

5. git push [alias] [branch] - After committing your changes locally, you can use git push to push commits to a remote repository. Additionally, you have the option to specify the remote alias (often "origin") and the branch you want to push your changes to (e.g., "main" or a specific "branch") by establishing an upstream relationship using the -u flag. Though not mandatory, this is useful as it allows you to use git push only without specifying the remote name and branch in the future.

   Example:

   $ git push -u origin main

6. git log - The git log command displays committed snapshots. It lets you list the project history, filter it, and search for specific changes. While git status lets you inspect the working directory and the staging area, git log only operates on the committed history.

   Example:

   $ git log --author="John Smith" -p hello.py

7. git config - The git config command is a convenience function that is used to set Git configuration values on a global or local project level. These configuration levels correspond to .gitconfig text files. Executing git config will modify a configuration text file.

   Example:

   $ git config user.email
   > $ git config --global user.email "[email protected]"