-
Notifications
You must be signed in to change notification settings - Fork 2
Workflow
So, you picked programming. There were about 4 different groups and you set upon this one. Well, I salute you, but that's not why I'm here. You came here because some executive told you to go read the wiki, it will explain what to do (Probably because they are too lazy to explain it themselves)
Workflow is defined as "The sequence of industrial, administrative, or other processes through which a piece of work passes from initiation to completion".(Google Search) We may not reach completion, but it's my job to reach initiation. Workflow in our case will be the path from good idea, to moving robot.
Github is an extension of an old program called Git. Git was a VCS(Version Control System) where you could label your changes, pass them on to someone else to check, and then implement the changes. Github is really just a bunch of servers in a dreary office space somewhere that all are holding people's code. Github is nice because it allows you to put all your code in a place where others can read it, and even suggest changes. Oh, and Octocat is the mascot.
Alright fine. Let's get into the meaty part of setting up your workflow system. I assume you already have Github. If you don't, shame on your programming lead. All of my instructions are gonna be in the command line, GUI is for losers. Open up the Github command line. It should bring you to a terminal in Windows Powershell©®™. When you install Github a folder is made in the documents folder. Make sure you can find the Github folder through your piles of documents.
At this point in the game you want to make sure that you have 'forked' the team repository (Don't worry, GitHub makes the pun for me). The team repository is located Here. Once it is forked there should be a new repository under your account that looks something like: [Username] / BIFTC2017-2018. Have your programing lead show you where the HTTP clone link is located (If you can find a moment of their Busy time) and copy that to clipbord. If you can't find it, the HTTP clone link is shown here on the far right in green:
Great. Don't worry, as it will all make sense soon. Now go back to your window of Windows powershell©®™. Powershell©®™ should put you in your documents folder, which should be fine. Type into the console:
dir
which will display the current contents of your directory. It should be empty, which might look something like this, or just move to the next line.
Mode LastWriteTime Length Name
---- ------------- ------ ----
If not, you probably know why. Once it has been confirmed empty, or it's not and you know what you are doing, then type:
git clone [whatever your HTTPS clone link is]
This will make a new folder (One level down from whatever you are in) and copies all the code exactly where it needs to be. Mainly, git clone is used due to all of the configuration that it does for us. This way our upstream targets, and most of the login information are done for us.
Quick Explanation:
On paper, what you have done is fairly straightforward. You downloaded the desktop application 'GitHub'. Using the command-line interface, you told git (Not GitHub): "Hey, go to this URL and grab everything there. Once we got it, put it in a folder that is one level lower than where we are. Oh, while your at it, please set all the configuration to match that link's repository". It is important to know where the Git and GitHub interactions are, and where they aren't. The clone link that you copied earlier was just the location of the repository (Being hosted by Github). If you really wanted, you could host your own little Git server at home, and use the HTTP clone link of that. The end function would still be the same.
Congratulations! You have successfully coped all the team code down to your local computer. You are now prepared to make your fame and fortune programming the robot to solve all sorts of technical challenges. This is where we part ways (Temporarily). Go off, and program. Once you are ready to institute those changes, check back here.
OK, you have come back to me. Presumably with amazing code that will rival all others. You showed it to your lead, and he snored at you or something...