Getting Started

1. 

   Go to Help → Perform Setup Tasks… and click Finish to set 6.031 defaults, including:

   • No tabs: use spaces instead of tabs, so your code looks the same in all editors regardless of how that editor displays tab characters.

   • Compiler warnings: enable extra warnings for mistakes you must avoid in this class.

   • Settings for Checkstyle and other plug-ins.

   Wait for the progress spinner at the bottom of the Eclipse window to complete.

2. Open Eclipse preferences.
   Windows and Linux: go to Window → Preferences.
   macOS: go to Eclipse → Preferences.

3. Make sure Eclipse is configured to use Java 10.

   1. In preferences, go to Java → Installed JREs. Ensure that “Java SE 10” or “10.0.2” is the only one checked. If it’s not listed, click Search.

   2. Go to Java → Compiler and set “Compiler compliance level” to 10. Click OK and Yes on any prompts.

4. Make sure assertions are always on. Assertions are a great tool for keeping your code safe from bugs, but Java has them off by default.

   In preferences, go to Java → Installed JREs. Select Java 10, click “Edit…”, and in the “Default VM arguments” box enter: -ea (which stands for enable assertions).

1. Click the Java Tutor tab next to Package Explorer.

   If you don’t see it: go to Window → Show View → Other…, select Java Tutor → Java Tutor and press OK. Then drag the Java Tutor view so it stacks with the Package Explorer, filling up the left side of the window.

2. Finish setting up the Java Tutor by copying and pasting your personal start URL

   

   into its location bar, and press Enter:

   

   You should see the tutor web interface appear:

3. 

   When you’re using the Tutor, be sure to bring Problems to the front, so that you can see Java compiler errors more easily. Your Eclipse window should look something like the window on the right.

1. 

   In the Quick Access field in the top right of your Eclipse window, enter “set up constellation” and select Set up Constellation.

2. 

   Your web browser should open a Constellation page that requires MIT certificates. Click the red button.

   If you see a “Waiting for pair…” dialog but your browser does not open, or if the wrong browser opens and you do not have certificates: first set a different browser as your default (e.g., make Safari your default browser if you want to use Chrome), then go back and set the desired browser as the default. Cancel “Waiting for pair…” and do “Set up Constellation” again to make sure the correct browser opens.

3. 

   After following the prompts, you should see a “Success” message in Eclipse to confirm that Constellation is ready to use.

• cd (stands for “change directory”)

  Changes the current directory. If you’re in a directory that has a subdirectory called hello, then cd hello moves into that subdirectory.

  Use cd .. to move to the parent directory of your current directory.

• pwd (“print working directory”)

  Prints out the current directory, if you’re not sure where you are.

  On a well-configured system, your current directory is displayed as part of the prompt that the system shows when it’s ready to receive a command. If that’s not the case on your system, post on Piazza to get help configuring your prompt.

• ls (“list”)

  Lists the files in the current directory.

  Use ls -l for extra information (a “long” listing) about the files. Use ls -a (stands for “all”) to show hidden files, which are files and subdirectories whose names begin with a period.

• mkdir (“make directory”)

  Creates a new directory in the current directory. To create a directory called goodbye, use mkdir goodbye.

• up arrow and down arrow

  Use up arrow to put the command you just ran back on the command line. You can now edit that command to fix a typo, or just press enter to run it again.

  Use the up and down arrow keys to navigate through your history of commands, so you never have to re-type a long command line.

Before using Git, we’ll do some required setup and make it behave a little nicer.

1. Who are you?

   Every Git commit includes the author’s name and e-mail. Make sure Git knows your name and email by running these two commands:

   git config --global user.name "Your Name"
   git config --global user.email username@mit.edu

2. Editing commit messages.

   Every Git commit has a descriptive message, called the commit message. Pick one of the two options below to set up your commit message editor.

   Option 1: set up an easy-to-use editor macOS and Linux: use nano nano is a simple text editor. It does not come with the Windows version of Git, so Windows users should choose a different option. To see if you have nano, try running: nano in the terminal. The result should be a simple editor with instructions at the bottom of the screen; quit with ctrl-X. If that worked: git config --global core.editor nano will configure Git to use the nano editor. The commands to use the text editor (like copy, paste, quit, etc.) will be shown on the bottom of the screen. The ^ symbol represents the ctrl key. For example, you can press ctrl-O to save (nano calls it “write out”) and then ctrl-X to quit. Windows: use Notepad You can change the default editor to Notepad with: git config --global core.editor notepad If you prefer to edit your commit messages in the terminal, choose Option 2 instead.

   Option 2: use Vim On macOS and Windows, your default editor will be Vim. On Linux, the default editor depends on your distribution. Vim is a popular text editor, but it’s tricky to use. To see if you have Vim, try running: vim in the terminal. You start in a mode called “normal mode”. You can’t immediately type anything into the file! In order to start typing, press i (stands for “insert”). This will bring you to “insert mode”, so named because in this mode you can type text into the file. When you are done typing, press esc. This will bring you back to “normal mode”. Once you’re back in normal mode, you can type commands that start with :. To save your work, type :w (stands for “write”) and press return. To exit (quit) Vim, type :q and press return. To save and quit in one command, combine them: type :wq and press return.

3. LOL.

   As we’ll see in step 7 of this guide, git log is a command for looking at the history of your repository.

   To create a special version of git log that summarizes the history of your repo, let’s create a git lol alias using the command (all on one line):

   git config --global alias.lol "log --graph --oneline --decorate --color --all"

   Now, in any repository you can use:

   git lol

   to see an ASCII-art graph of the commit history.

1. Visit github.mit.edu and log in.

   GitHub (at github.com) is a popular site for hosting remote Git repositories. MIT’s GitHub Enterprise site (at github.mit.edu) runs the same software, but you log in with your MIT account.

   Your problem set and project repositories for 6.031 will be stored on github.mit.edu.

2. From the menu at the top right corner of the page, go to Settings, and select SSH and GPG keys.

3. Follow the GitHub Enterprise instructions to set up SSH:

   1. Check if you already have SSH keys

   2. Generate a SSH key if you don’t have one

   3. Add the SSH key to your account (make sure you are working on github.mit.edu, not github.com)

   4. Test the SSH connection (hostname is github.mit.edu)

Git is a version control system (VCS). The Pro Git book describes what Git is used for:

Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. […] It allows you to revert files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more. Using a VCS also generally means that if you screw things up or lose files, you can easily recover.

Some of the most important Git concepts:

• repository: A folder containing all the files associated with a project (e.g., a 6.031 problem set or team project), as well as the entire history of commits to those files.

• commit (or “revision”): A snapshot of the files in a repository at a given point in time.

• add (or “stage”): Before changes to a file can be committed to a repository, the files in question must be added or staged (before each commit). This lets you commit changes to only certain files of your choosing at a time, but can also be a bit of a pain if you accidentally forget to add all the files you wanted to commit before committing.

• clone: Since Git is a “distributed” version control system, there is no concept of a centralized Git “server” that holds the latest official version of your code. Instead, developers “clone” remote repositories that contain files they want access to, and then commit to their local clones. Only when they push their local commits to the original remote repository are other developers able to see their changes.

• push: The act of sending your local commits to a remote repository. Again, until you add, commit, and push your changes, no one else can see them.

• pull: The act of retrieving commits made to a remote repository and writing them into your local repository. This is how you are able to see commits made by others after the time at which you made an initial clone.

You start working with Git repos in 6.031 by cloning a remote repository into a local repository on your computer.

To do this, open the terminal (use Git Bash on Windows) and use the cd command to change to the directory where you would like to store your code. Then run:

git clone URI-of-remote-repo

or

git clone URI-of-remote-repo project-name

Replace URI-of-remote-repo with the location of the remote repository, and replace project-name with the appropriate project name, like ps0. The result will be a new directory project-name with the contents of the repository. This is your local repository.

After you have cloned a repository, you should navigate into the repository on your command prompt using cd. This lets you run git commands on the repository.

Cloning problem sets: for each problem set in 6.031, you will have a Git repository on Athena.

Initially this remote repository only contains some template code.

To start working on the problem set, you will clone that repository onto your machine.

As you complete each part of the problem set, you will commit your changes to the local repository and then push them to the remote repository.

When the time comes for grading your assignment, we will clone the remote repository and look at the last commit you made and pushed there before the deadline.

The basic building block of data in Git is called a “commit”. A commit represents some change to one or more files (or the creation or deletion of one or more files).

When you change a file or create a new file, that change is not part of the repository. Adding it takes two steps. First, run:

git add file.txt (where file.txt is the file you want to add)

You’ll either need to run that command from the same directory as the file, or include directory names in the file path.

This stages the file. Second, once you’ve staged all your changes, run:

git commit

This will pop up the editor for your commit message. When you save and close the editor, the commit will be created.

Git has some nice commands for seeing the status of your repository.

The most important of these is git status. Run it any time to see which files Git sees have been modified and are still unstaged and which files have been modified and staged (so that if you git commit those changes will be included in the commit). Note that the same file might have both staged and unstaged changes, if you changed the file more after running git add.

When you have unstaged changes, you can see what the changes were (relative to the last commit) by running git diff. Note that this will not include changes that were staged (but not committed). You can see those by running git diff --staged.

After you’ve made some commits, you’ll want to push them to a remote repository. In 6.031, you should have only one remote repository to push to, called origin. To push to it, you run the command:

git push origin master

The origin in the command specifies that you’re pushing to the origin remote. By convention, that’s the remote repository you cloned from.

The master refers to the master branch. We won’t use branches in 6.031. master is Git’s default branch name, so all our commits will be on master, and that’s the branch we want to push.

Once you run this, you will be prompted for your password and hopefully everything will push. You’ll get a line like this:

a67cc45..b4db9b0  master -> master

Sometimes, when you try to push, things will go wrong. You might get an output like this:

! [rejected]      master -> master (non-fast-forward)

What’s going on here is that Git won’t let you push to a repository unless all your commits come after all the ones already in your remote repository. If you get an error message like that, it means that there is a commit in your remote repository that you don’t have in your local one (on a project, probably because a teammate pushed before you did). If you find yourself in this situation, you have to pull first and then push.

To perform a pull, you should run git pull. When you run this, Git actually does two things:

1. It downloads the changes and stores them in its internal state. At this point, the repository doesn’t look any different, but it knows what the state of the remote repository is and what the state of your local repository is.

2. It incorporates the changes from the remote repository into the local repository by merging, described below.

If you made some changes to your repository and you’re trying to incorporate the changes from another repository, you need to merge them together somehow. In terms of commits, what actually needs to happen is that you have to create a special merge commit that combines both changes. How this process actually happens depends on the changes.

If you’re lucky, then the changes you made and the changes that you downloaded from the remote repository don’t conflict. For example, maybe you changed one file and your project partner changed another. In this case, it’s safe to just include both changes. Similarly, maybe you changed different parts of the same file. In these cases, Git can do the merge automatically. When you run git pull, it will pop up an editor as if you were making a commit: this is the commit message of the merge commit that Git automatically generated. Once you save and close this editor, the merge commit will be made and you will have incorporated both changes. At this point, you can try to git push again.

Sometimes, you’re not so lucky. If the changes you made and the changes you pulled edit the same part of the same file, Git won’t know how to resolve it. This is called a merge conflict. In this case, you will get an output that says CONFLICT in big letters. If you run git status, it will show the conflicting files with the label Both modified. You now have to edit these files and resolve them by hand.

First, open the files in Eclipse. The parts that are conflicted will be really obviously marked with obnoxious <<<<<<<<<<<<<<<<<<, ==================, and >>>>>>>>>>>>>>>>>> lines. Everything between the <<<< and the ==== lines are the changes you made. Everything between the ==== and the >>>> lines are the changes you pulled in. It’s your job to figure out how to combine these. The answer will of course depend on the situation. Maybe one change logically supercedes the other, or maybe they can be merged somehow. You should edit the file to your satisfaction and remove the <<<</====/>>>> markers when you’re done.

Once you have resolved all the conflicts (note that there can be several conflicting files, and also several conflicts per file), git add all the affected files and then git commit. You will have an opportunity to write the merge commit message (where you should describe how you did the merge). Now you should be able to push.

You can see the list of all the commits in the repository (with their commit messages) using git log. You can see the last commit on the repository using git show. This will show you the commit message as well as all the modifications.

Long output: if git log or git show generate more output than fits on one page, you will see a colon (:) symbol at the bottom of the screen. You will not be able to type another command! Use the arrow keys to scroll up and down, and quit the output viewer by pressing q.

Commit IDs: every Git commit has a unique ID, the hexadecimal numbers you see in git log or git show. The commit ID is a unique cryptographic hash of the contents of that commit. Every commit, not just within your repository but within the universe of all Git repositories, has a unique ID (with extremely high probability).

You can reference a commit by its ID (usually just by the first few characters). This is useful with a command like git show, where you can look at a particular commit rather than only the most recent one.

You will also see commits identified by ID in tools like GitHub.mit and Didit.

If you’d like to practice using the version history to undo a change:

---

We will revisit Git and learn more about version control in future classes. If you’ve installed the software, set up Eclipse, and completed the GitStream exercises above, you’re ready to move on to Problem Set 0.