MATTHEW MCGOVERN

				
					#Some basic commands for starting with git:

gi𝘁 𝗶𝗻𝗶𝘁  

#initializes a new Git repository in your current directory.

𝗴𝗶𝘁 𝗰𝗹𝗼𝗻𝗲 <𝗿𝗲𝗽𝗼> 

# clone (copy) it to the machine your working on

#𝗠𝗮𝗸𝗲 𝗖𝗵𝗮𝗻𝗴𝗲𝘀

𝗴𝗶𝘁 𝘀𝘁𝗮𝘁𝘂𝘀 

#It is a recommended practice to review the status of your files before or after making changes. Easily identify any modifications that have not been staged yet.

𝗴𝗶𝘁 𝗮𝗱𝗱 <𝗳𝗶𝗹𝗲𝗻𝗮𝗺𝗲> 

# stage files for a commit. 

𝗴𝗶𝘁 𝗮𝗱𝗱 . 

𝗴𝗶𝘁 𝗮𝗱𝗱 -𝗔 

#add all  changed files to the stage 

𝗴𝗶𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 -𝗺 "commit message" 

#commit files with a descriptive message.

#𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴

𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵 

# list all the local branches in current repo

𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵 <𝗯𝗿𝗮𝗻𝗰𝗵𝗻𝗮𝗺𝗲>

#create new branch

git checkout <branchname>

# Change to another branch

git merge <branchname> 

#merge changes to (usually master) main branch

#𝗥𝗲𝗺𝗼𝘁𝗲 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝗶𝗲𝘀

git remote add origin <repo url>

𝗴𝗶𝘁 𝗿𝗲𝗺𝗼𝘁𝗲 -𝘃 

#check which remote servers are connected with your local repository.

#connect to remote repo. Can also use:

git remote set-url --add <name> <url>
git remote set-url --delete <name> <url>

𝗴𝗶𝘁 𝗽𝘂𝘀𝗵 𝗼𝗿𝗶𝗴𝗶𝗻 <𝗯𝗿𝗮𝗻𝗰𝗵𝗻𝗮𝗺𝗲> 

#This command sends your commits to the remote repository.

𝗴𝗶𝘁 𝗽𝘂𝗹𝗹 

#Pull will grab and merge any changes from the remote repository.

git fetch 

#downloads changes from a remote repository without integrating them. git pull incorporates downloaded changes by merging them into the local files.

git merge 

#combines branches by creating a new commit, preserving the commit history. 

git rebase 

#moves or combines commits onto a new base

git reset 

#discards local changes completely by moving the branch pointer. 

git revert 

#undoes changes by creating a new commit that reverses the effects, preserving the commit history.

#example to add one file to repo from working machine, where git is initialized.

git add shopping_list.yml
git commit -m "new file"
git push origin main

#.gitignore: 

#The .gitignore file is used to exclude certain files and directories from being tracked by Git. 
#It uses pattern matching rules to specify what should be ignored.
#By adding filenames, extensions, or directory names to the .gitignore file, 
#you can prevent them from being committed and pushed to the repository. 
#This helps keep the repository clean and avoids including irrelevant or sensitive files in the version history.




</url></name></url></name></repo></branchname></branchname>