{"action":"created","issue":{"url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/issues/8","labels_url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/issues/8/comments","events_url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/issues/8/events","html_url":"https://github.com/1point618/exemplar-prototype-barney/issues/8","id":115360731,"number":8,"title":"Lesson 3: The GitHub Workflow","user":{"login":"1point618","id":876894,"avatar_url":"https://avatars.githubusercontent.com/u/876894?v=3","gravatar_id":"","url":"https://api.github.com/users/1point618","html_url":"https://github.com/1point618","followers_url":"https://api.github.com/users/1point618/followers","following_url":"https://api.github.com/users/1point618/following{/other_user}","gists_url":"https://api.github.com/users/1point618/gists{/gist_id}","starred_url":"https://api.github.com/users/1point618/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/1point618/subscriptions","organizations_url":"https://api.github.com/users/1point618/orgs","repos_url":"https://api.github.com/users/1point618/repos","events_url":"https://api.github.com/users/1point618/events{/privacy}","received_events_url":"https://api.github.com/users/1point618/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/labels/learning","name":"learning","color":"fbca04"}],"state":"open","locked":false,"assignee":{"login":"bpbarrett","id":15677021,"avatar_url":"https://avatars.githubusercontent.com/u/15677021?v=3","gravatar_id":"","url":"https://api.github.com/users/bpbarrett","html_url":"https://github.com/bpbarrett","followers_url":"https://api.github.com/users/bpbarrett/followers","following_url":"https://api.github.com/users/bpbarrett/following{/other_user}","gists_url":"https://api.github.com/users/bpbarrett/gists{/gist_id}","starred_url":"https://api.github.com/users/bpbarrett/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bpbarrett/subscriptions","organizations_url":"https://api.github.com/users/bpbarrett/orgs","repos_url":"https://api.github.com/users/bpbarrett/repos","events_url":"https://api.github.com/users/bpbarrett/events{/privacy}","received_events_url":"https://api.github.com/users/bpbarrett/received_events","type":"User","site_admin":false},"milestone":null,"comments":2,"created_at":"2015-11-05T19:52:58Z","updated_at":"2015-11-05T19:53:18Z","closed_at":null,"body":"Let's dig into the GitHub Workflow so that you can help us add a feature to our website. This will give you both a conceptual understanding of how GitHub works, as well as experience using the GitHub Workflow with a team.\r\n\r\nTo start off, [open this link in a new tab](https://guides.github.com/introduction/flow/) to read up on the GitHub Workflow. Pay special attention to the sections on Branches, Commits, and Pull Requests. We're using the Branching workflow, so don't worry about the refernces to the Forking workflow.\r\n\r\nNow that you've read it, did some of it seem familiar? When fixing the bug, you did all these steps, although they were crammed together. You created a branch and committed to it at the same time, you went directly to creating a pull request, then I commented on the PR, and you merged it successfully. We didn't need to deploy it to production, because I could view the README right on GitHub, which is what I did to verify that what you'd done was correct.\r\n\r\nThe flow we went through, creating a branch and committing to it at the same time, really only works for small fixes that you want to merge right away. For longer projects where we'll have multiple commits, we'll want to create a new branch first, then commit the various files to that branch.\r\n\r\nEnough talk, let's get started! Go to the Issue View and assign yourself the Issue called **Users should be able to email us if they want to get in touch**. In that Issue, we'll discuss the work that needs to get done in order to get the new feature up and running.\r\n\r\nThis issue will stay here as a repository for everything you've learned so far. You can go through the comments below to find resources on Issues, Commits, Branches, and more. Go ahead and leave it open or close it, it's up to you—either way you'll be able to come back to it to review the work you've done."},"comment":{"url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/issues/comments/154172029","html_url":"https://github.com/1point618/exemplar-prototype-barney/issues/8#issuecomment-154172029","issue_url":"https://api.github.com/repos/1point618/exemplar-prototype-barney/issues/8","id":154172029,"user":{"login":"1point618","id":876894,"avatar_url":"https://avatars.githubusercontent.com/u/876894?v=3","gravatar_id":"","url":"https://api.github.com/users/1point618","html_url":"https://github.com/1point618","followers_url":"https://api.github.com/users/1point618/followers","following_url":"https://api.github.com/users/1point618/following{/other_user}","gists_url":"https://api.github.com/users/1point618/gists{/gist_id}","starred_url":"https://api.github.com/users/1point618/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/1point618/subscriptions","organizations_url":"https://api.github.com/users/1point618/orgs","repos_url":"https://api.github.com/users/1point618/repos","events_url":"https://api.github.com/users/1point618/events{/privacy}","received_events_url":"https://api.github.com/users/1point618/received_events","type":"User","site_admin":false},"created_at":"2015-11-05T19:53:18Z","updated_at":"2015-11-05T19:53:18Z","body":"# Branches\r\n\r\nBranching is an essential part of the way that we work on GitHub. Rather than having everyone write code to the same place, we create branches for each piece of work, commit code there, then merge them into the main branch once they're done.\r\n\r\nBranches should have descriptive names so that you know what work is getting done on which branch. By convention, the main branch is usually called `master` on GitHub projects. When you see people talking about master, they're just talking about a specific branch. "}}