Now that you have a personal domain and page, let's work together on a map. The purpose here is to introduce you to Git Flow which we will be using from now on!
🚀 steps to definitely pay attention to
💻 run this in Terminal
🍸 pro tip
Here's what we're going to do!
- Clone The Repo
- Start Local Webserver
- Create a new branch
- Merge Conflicts
- Add some JS to Map
- Rebase to pull new changes
- Push branch to github
- Create pull request
- 🚀 Clone the repo:
git clone [email protected]:dartmouth-cs52-21S/git-map.git - 🚀 change directory to this new workspace:
cd git-map
🐛 if you run into trouble with messages about ssh keys you'll notice in the URL above we use [email protected]:. This is running git over SSH. This has some nice security features, but if you prefer HTTPS you can use:
git clone https://github.com/dartmouth-cs52-21S/git-map.git instead. For SSH you'll need to configure your ssh keys ssh-keygen -t rsa -b 4096 -C "[email protected]" (hit enter a bunch of times — don't use a password) and upload that key to github.
If you run git config --global user.email and it gives you some weird email address you should fix this by running:
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
And make sure the email you choose is also listed in GitHub Email Settings
💻 python -m SimpleHTTPServer 9000
Serving HTTP on 0.0.0.0 port 9000 ...
127.0.0.1 - - [09/Jun/2016 18:25:18] "GET / HTTP/1.1" 200 -*Note: in python3 do python -m http.server 9000
Let's check out what we have made in Chrome: http://localhost:9000
As you edit this, keep checking and make sure you aren't pushing a broken site.
We're doing something a little different with git this time. You are modifying a file that other people might be working on, thus the potential for a merge conflict arises. The default flow for collaborating with others is:
git commityour local workgit pullto get any upstream commits (commits that exist on github but not on your computer yet)- resolve any conflicts that might have arisen
git addconflicted file to mark them as resolvedgit commityour changesgit pushyour changes up to github
However! We will be doing a slightly modified flow using feature branches.
It will go something like this:
git branchto create a new branch of code to work ingit commityour local workgit pull --rebaseto merge any upstream main branch commits onto your branch- resolve any conflicts that might have arisen
git addconflicted files to mark them as resolvedgit commityour changesgit pushyour branch up to github- create a pull request on github
- get your pull request from your feature branch merged into the main branch
Here we go through a more in depth git flow that includes code branches and pull requests. In general if your team is larger than 2 people you should definitely use this!
We're going to create a branch now and try out this new workflow.
Start a local feature branch and do work on it. A branch keeps your work separate from the main (usually called master) branch. Think of this as a tree where the master branch can be thought of as the main trunk.
Here is a great visualization tool to help see what you are doing in the git tree: git-with-d3
💻 git branch <featurename> # creates new branch feature
💻 git checkout <featurename> # switches to branch feature🍸 Protip: git checkout -b will both create a new branch and check it out to make it the current branch you are working on.
🍸 Protip: git branch will show which branches exist and which you're on (the *).
🚀 lets name our branch feature with yourname_icon! git checkout -b yourname_icon. (lowercase and no spaces)
🚀 if you do git branch you should see * yourname_icon.
🍸 Protip: Periodically pull in changes from origin/main and update your feature branch.
Note that these commands only update your current local branch. The idea here is to not fall too far behind the master branch if other people are working on it.
💻 git pull origin mainAt this point after a git pull you may get a message that looks like this:
CONFLICT (content): Merge conflict in somefile
Automatic merge failed; fix conflicts and then commit the result.
This is when the fun starts. How do you fix this?
The cause for merge conflicts is that you edited the exact same line/s as someone else and git doesn't know how to automatically resolve that. This happens and is normal, don't worry. So to fix you just need to pick apart the conflict and merge it in — continue to the next section to see how this happens!
If you were to do this by hand, git takes the pretty code you wrote and injects terrible "conflict markers" that look like this:
<<<<<< HEAD
var h = 'hello, world';
======
var h = 'Hi!';
>>>>>> cb1abc6bd98cfc84317f8aa95a7662815417802dwhere the line between <<<HEAD and ==== is the line/lines of code that are relevant in your file, and between ==== and >>>> cb1abc6 are from the remote repository (the repository that you see on github.com). The crazy characters refer to the commit id hash that the change comes from.
What you want to do is get rid of all the crazy stuff and make sure the lines you have left are logical code, in this case you probably want to decide between the two versions. In some cases you need to be aware of what changed around, be sure to read the code for logic and syntax and check that it works locally after you fix it.
VSCode has a nice builtin tool to help you resolve merge conflicts shown here:
Once you have your conflict file the way you want it — ie. fixed and without any more of the conflict markers...
- All you have to do to continue is:
git add thefixedfilewhich indicates to git that you have resolved the conflict. Thengit commitwith no options will complete the merge and automatically create a commit message.
Now lets add a picture of yourself and a lat long for a place that you like or are from.
🚀 Open up one of the people-#.json files in VSCode (it doesn't matter which one).
🚀 Add a new JSON object for yourself. You can start by copy pasting a previous object -- this is the 15 or so lines of text inside the curly braces.
Add an image of yourself into iconURL. It would probably be a good idea to resize your image to be 200x200 pixels. If you don't have a favorite tool for this try resizeimage
For the url field use the new page that you made earlier! Rather than using http:// or https:// just start the url with //. The browser will then match the protocol (http or https) to how the page was loaded and thus avoid errors about insecure resources.
Find a lat long: http://www.latlong.net/
🚀 Play around with it till you have a working badge visible on your local dev site: http://localhost:9000/ and when you click on the badge it is able to load in the page you made into the modal.
If you get an error on the webpage or nothing displaying, then most likely something in the code is broken. This can be that the JSON is malformed, an extra comma or merge conflict markers.
If you have trouble with json - you can run it through a validator to make sure the syntax is ok.
If nothing displays on the webpage, the first thing to do is open the chrome debug console and look for error messages.
When you're nearly ready to publish, rebase your local branch on top of the latest main one more time. Just like you have been above. Note: we are using rebasing here instead of just pulling, because now we are pros. 🏆 What this does is basically pull in all remote changes and then replay your commits on top of them. This gives you a cleaner version history. Don't forget to git add and git commit your changes before pulling in new changes (it'll warn you though).
💻 git pull --rebase origin mainIf you have rebase conflicts, fix the files as in Deciphering-Merge-Conflicts and do git add to indicate to git that you have resolved things, then git rebase --continue. Repeat until you're all good.
After you are finished working on your branch, you should push it up to github.
💻 git push origin yourname_icon🍸 Protip: git does not push multiple branches by default, but you can with: git push --all origin. Just be careful if you have a ton of test branches lying around.
The best way to merge your feature into the main branch is to issue a pull request. This bundles up your feature branch into a request that you or someone else on your team can approve.
🚀 Go to the Github Repo Page (or use the Github Desktop App) and submit a New Pull Request (choosing whatever branch you just pushed), add a quick description. Possibly do code review or just approve the request yourself. The idea here is that this is a checkpoint spot before adding your feature to the main branch so that everybody on your teams knows what is happening.
To do a code review, @mention a peer in the pull request. Once approved, your code changes will be merged. You can also merge pull requests after carefully reviewing all the changes.
Alternatively you can merge your changes in to the main branch without a pull request, but this should only be done if you are using git on your own or with a very small team!
git checkout main
git merge your_feature_branch_nameOnce you no longer need a branch you should delete it! You can do this on github.
You can also do this locally with git branch -d your_feature_branch_name.
Note: you have to delete it in both places, as just deleting it remotely won't delete it locally.
Once your changes are merged into the remote main branch on github you'll be able to see your changes at: http://map.cs52.me
If you want more practice try: https://learngitbranching.js.org
To edit code ~/.gitconfig
[user]
name = John Doe
email = [email protected]
[alias]
p="pull --rebase origin" # tweak naming to whatever, but a nice shortcut to ensure --rebase
co="checkout"
st="status"
br="branch"
[branch]
autosetuprebase = always # set rebase to be default for new branchesYou might want to consider cleaning up your local branch history. It's a good idea to commit frequently as checkpoints to save your work, but if you have a lot of them, the shared repo history will look cleaner without them.
A nice way to visualize your commits and branches locally is git log --graph --oneline. Alternatively, use a GUI like GitX (http://rowanj.github.io/gitx/).
Then, rebase with up git "interactive" mode, which will pull up your text editor.
git rebase -i mainOR
git rebase -i HEAD~Xwhere X is the number of commits back you want to roll back, OR
git rebase -i xxxxxxwhere xxxxxx is the commit id, which you can get from git log.
To squash a commit into the previous one, replace "pick" with "s" or "squash" and save the file.
This is the screen you will see after typing git rebase -i.
This file will be launched in your default text editor.
You have many different options, typically squash is the most useful.
By changing the character in front of the second commit to s,
we are "combining" the second commit into the first commit.
To finish, save and exit on your text editor (:wq in Vim).
After squashing, you have to write a new commit message. Again to finish, save and exit on your text editor. Done!
Note: this can cause problems if you've pushed your branch to your remote repo, since you are rewriting commit history in your local branch and this will mismatch with the remote repo's history. Best to do this before pushing, but if you've done a rebase commit squash on commits that you already pushed, then the next time you push to the remote repo you will have to do a forced update git push -f origin feature. However be aware that this is dangerous and anyone else working on this feature branch will have issues pushing their branch. One solution to this is asking them to stash their commits and then rebase after you push your branch. You've been warned.
git push -u origin <feature>-u is short for --set-upstream, which will set up your local branch to pull automatically from this newly pushed branch. However it's optional.
git push origin --delete <feature>git branch -D <feature>git checkout <feature> # shorter version, works with newer versions of GitBe careful about this!! You will lose your local changes.
git reset --hard mybranch goodbranch
git reset --hard main origin/main Sometimes you commit to the wrong branch. Figure out the commit ID of the commit you want to grab.
git cherry-pick <COMMIT ID>- Try to use
git rebasecommands when possible rather thangit merge, so we can have a cleaner and more linear Git commit history (that said, merge commits do have their place). - Use local branches to do most of your more involved work (this also lets you quickly switch between different features, or pause work on a feature to work on a bug fix).
- The general idea is to try to resolve conflicts locally (by pulling in changes from the shared repo before pushing), so merging into master (either manually or by Github pull request merge should be simple and automatic)
- If you are doing a complex rebase merge fix, if you squash your commits first (see earlier notes about rebase interactive), you can do your manual merge fixes in fewer, as there are fewer commits to have to edit. Otherwise you may be opening your text editor a lot.
- Add the following to your
.bash_profileto see your current branch and status within the command line prompt:
# Prompt to add branch and status to the command line
COLOR_RED="\[\e[31;40m\]"
COLOR_GREEN="\[\e[32;40m\]"
COLOR_CYAN="\[\e[36;40m\]"
COLOR_RESET="\[\e[0m\]"
function git_branch_name {
ref=$(git symbolic-ref HEAD 2> /dev/null) || return
echo " ("${ref#refs/heads/}")"
}
function git_branch_color {
if [[ $(git status 2> /dev/null | grep -c :) == 0 ]]
then echo "${COLOR_GREEN}"
else echo "${COLOR_RED}"
fi
}
function prompt_title {
PS1="\w$(git_branch_color)$(git_branch_name)${COLOR_RESET} \$ "
}
PROMPT_COMMAND=prompt_titleThis will allow you to do git checkout TAB for a list of branches. First, download the git autocompletion support for bash.
curl https://raw.githubusercontent.com/git/git/master/contrib/completion/git-completion.bash -o ~/.git-completion.bashThen, add the following to your ~/.bash_profile.
if [ -f ~/.git-completion.bash ]; then
. ~/.git-completion.bash
fiMore information can be found here
Thanks to the many contributors to this over the years: