CreatorDB | Base on mit-6.830-2021 , see https

You should have Git installed from the previous section. If you don’t know Git that well, this probably seemed very arcane. Just keep using Git and you’ll understand more and more. You aren’t required to use commands like commit and push as you develop your labs, but will find them useful for debugging. We’ll provide explicit instructions on how to use these commands to actually upload your final lab solution.
The first thing we have to do is to clone the current lab repository by issuing the following commands on the command line: ```bash $ git clone https://github.com/MIT-DB-Class/simple-db-hw-2021.git ``` Now, every time a new lab or patch is released, you can ```bash $ git pull ``` to get the latest. That's it. You can start working on the labs! That said, we strongly encourage you to use git for more than just downloading the labs. In the rest of the guide we will walk you through on how to use git for version-control during your own development.
Notice that you are cloning from our repo, which means that it will be inappropriate for you to push your code to it. If you want to use git for version control, you will need to create your own repo to write your changes to. Do so by clicking New on the left in github, and make sure to choose Private when creating, so others cannot see your code! Now we are going to change the repo we just checked out to point to your personal repository.
By default the remote called origin is set to the location that you cloned the repository from. You should see the following: ```bash $ git remote -v origin https://github.com/MIT-DB-Class/simple-db-hw-2021.git (fetch) origin https://github.com/MIT-DB-Class/simple-db-hw-2021.git (push) ``` We don't want that remote to be the origin. Instead, we want to change it to point to your repository. To do that, issue the following command: ```bash $ git remote rename origin upstream ``` And now you should see the following: ```bash $ git remote -v upstream https://github.com/MIT-DB-Class/simple-db-hw-2021.git (fetch) upstream https://github.com/MIT-DB-Class/simple-db-hw-2021.git (push) ```
Lastly we need to give your repository a new origin since it is lacking one. Issue the following command, substituting your athena username: ```bash $ git remote add origin https://github.com/[your-repo] ``` If you have an error that looks like the following: ``` Could not rename config section 'remote.[old name]' to 'remote.[new name]' ``` Or this error: ``` fatal: remote origin already exists. ``` This appears to happen to some depending on the version of Git they are using. To fix it, just issue the following command: ```bash $ git remote set-url origin https://github.com/[your-repo] ``` This solution was found from [StackOverflow](http://stackoverflow.com/a/2432799) thanks to [Cassidy Williams](https://github.com/cassidoo). For reference, your final `git remote -v` should look like following when it's setup correctly: ```bash $ git remote -v upstream https://github.com/MIT-DB-Class/simple-db-hw-2021.git (fetch) upstream https://github.com/MIT-DB-Class/simple-db-hw-2021.git(push) origin https://github.com/[your-repo] (fetch) origin https://github.com/[your-repo] (push) ```
Let’s test it out by doing a push of your master branch to GitHub by issuing the following: ```bash $ git push -u origin master ``` You should see something like the following: ``` Counting objects: 59, done. Delta compression using up to 4 threads. Compressing objects: 100% (53/53), done. Writing objects: 100% (59/59), 420.46 KiB | 0 bytes/s, done. Total 59 (delta 2), reused 59 (delta 2) remote: Resolving deltas: 100% (2/2), done. To git@github.com:MIT-DB-Class/homework-solns-2018-<athena username>.git * [new branch] master -> master Branch master set up to track remote branch master from origin. ```
That last command was a bit special and only needs to be run the first time to setup the remote tracking branches. Now we should be able to just run git push without the arguments. Try it and you should get the following: ```bash $ git push Everything up-to-date ```