Right now, this repository locally has no knowledge of the remote repo we first created on - we’re going to change that now by going to your GitHub repository, in the right sidebar, copy the remote repository URL: git remote add origin git status git remote -v this verifies the new remote URL git push origin master this pushes the changes in your local repository up to the remote repository you specified as the origin terms not going over today: Forking: allows you as a Github user to begin helping an existing open source project (you can even fork those that say they have read-only access and ask for permission later to contribute, by submitting a “pull request”). txt is now merged into the branch, (in this case the master branch, that lives now on your local machine). git commit -m “my first commit” <- anything within the quotes is a desription of what happened to that document, in case you want to roll back changes and to describe what happened to others who might look at your public repo. #BAVC QCTOOLS CODE#txt file) git status to check - now we’re at the point where there are changes we want to add to the rest of the application, feel good about its affect and intention enough in the code to do that. That doesn’t mean that it’s a permanent record of that file yet (kind of like a suggestion - adding it to the record and saving w/ more ease of working and futzing around without impacting other parts of the application or whatever else is in the repo that might function alongside this. First, we can check the status of the tracking of this doc by typing “git status” git status examines the working directory to look for files that are modified or are new git add video.txt adds the file to version control - to that local hidden. In order to track it as a part of our git repo, we have to take some deliberate actions. Now at this point, it is untracked but in the same folder as the. We open a text editor (any), make the file video.txt. git, that is in that same folder to track whatever else is in it). txt file in the directory we just created, amia14 (not. info-objects-ref are where these versions are stored. git - it’s hidden, used as a way to store versions. git by using application called “tree” to see files used to help versioning. #BAVC QCTOOLS MAC#git config -global user.name "laurensorensen" <- username from Github sign-up git config -global user.email <- email used with Github Files that are hidden in a Mac are labeled with a period in front: Show. By signing up for Github, we haven’t done any copying of code or capturing of code. git Triggered by actions you take to make versions that are captured in this local directory (still local right now - Github is just the networked part). Commands in command line are labelled in bold: You can initialize a local repository by typing git init -The way git works is that it uses the filesystem to create a top level directory, that you control locally -So in typing git init having cd’ed into a a directory (using mkdir) called amia14 and there’s a nested folder beneath it called. There are also many tutorials out there, I’ll link to in a later slide. What follows are some simple instructions. Sign up for an account here: - and create a repo! Don’t create a readme.md. #BAVC QCTOOLS HOW TO#We’re going to run through a quick demo of how to use Git and Github. Github is: a social way to share versions of things (things being: historically mostly code and associated documentation), so making that community contribution easier. There are multiple checks, called “pushing” and “pulling” that those who are “committers” to a particular repo or application can gather from others in the community that wish to contribute. #BAVC QCTOOLS SOFTWARE#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |