Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions _posts/journal-week-7.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
##Journal Week 7

Working in groups this week was both challenging and great. While the logistics of having multiple people working on one assignment at once made things a nightmare at times, I really enjoyed learning the git flow process. I found I became much more mindful of everything I did because I knew that it effected not only my code but others' as well.

Being a team leader was very insightful. Having to focus on the big picture and not an individual task was a great exercise in how to view an assignment.
Too often I focus on each individual task, connecting them when they are all complete, only to find out that things don't work as well together as I had hoped.
I really enjoyed being able to help my teammates work through problems they might be having. Though it was hard not to being coding, not having to work on my own
file meant that I had the time to really help out and trouble shoot some difficult things. I also was able to do research and come up with different solutions while my
teammates kept working. In the end I found this accelerated the processes tremendously.

Working with a team leader also had many benefits as well. When I found myself stuck on something I knew I had someone there
to help work through it which was invalueable. I also found that having someone keeping an eye on the big picture was
extremely helpful. Often times they would give suggestions on things that would benefit us down the road, like more semantic
html tags or specific selectors in sass.

All in all I found my experience working in groups to be rewarding. I learned a great deal in a shorter time frame just by having a few
collaborating with others on a task.



11 changes: 11 additions & 0 deletions _posts/resource-week-7.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
##Resource Week 7

For this week's resource I would like to highlight a site that allows you to write, test, and tweak **Regular Expressions** or **RegEx**.

http://regexr.com/

On the left is a menu with references, cheatsheets, examples, and more. The main section to the right is where you can write
RegEx to test on example text which you can replace with your own.

There is also a video tutorial for how to use the site.

50 changes: 50 additions & 0 deletions _posts/tutorial-week-7.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
##[How to Authenticate GitHub on the Terminal with Git](https://help.github.com/articles/caching-your-github-password-in-git/)

Maybe you've just signed up for GitHub and installed Git to use on your command line or perhaps you have been using
both for a while but never set up your terminal so you wouldn't have to retype your username and password every time you
`git push`. There are two methods to do this: Connecting over HTTPS which is recommended by GitHub, and connecting over SSH.
This tutorial will use the HTTP method.

1. First you need to verify that you have osxkeychain installed on your computer. You can do this by typing the following command
into your terminal.

`$ git credential-osxkeychain`

If it _is_ available it will return:

`Usage: git credential-osxkeychain <get|store|erase>`

Move to step 3.

If _not_ it will return:

`git: 'credential-osxkeychain' is not a git command. See 'git --help'.`

2. If it is _NOT_ installed then install it using curl in the terminal like this:
```
$ curl -s -O \
https://github-media-downloads.s3.amazonaws.com/osx/git-credential-osxkeychain
```
This will download the helper. Next type:

`chmod u+x git-credential-osxkeychain`

This will fix the permissions so it can run.

3. Once you have it installed we need to move it to the same directory that Git is in.

```
$ sudo mv git-credential-osxkeychain \
"$(dirname $(which git))/git-credential-osxkeychain"
```
`sudo` is a command giving you ultimate authority to move the helper. `which git` gets the command path (location) of git
so that we can move the helper there.

At this point your terminal will ask for a password. This is the password to your computer and not the password you use for github.

4. The last step is to tell Git to use the helper aka osxkeychain globally.

`$ git config --global credential.helper osxkeychain`

5. Now the next time you are asked to enter your username and password for Github it will store this information in your keychain
so you will no longer be required to type it in anymore.