This repo is for our Women Who Code 2017 Intro to Contributing to Open Source Workshop. This repo serves as a safe test space for those who wish to practice git, making pull requests and responding to issues.

• Overviewing GitHub and Releases
• Reviewing the Basics and Learning a Codebase
• Your First Open Source Project Commit (look for First Timer's Only PRs)
• What to expect - will my PR be merged in right away? How do deal with feedback?
• Becoming a Regular Contributor

In the Issues tab, we have a variety of issues with different labels that you can choose. Choose from any of the labels and submit a PR with your changes. We'll review your PR and conduct a mock code review, before ultimately merging your PR.

If you have any questions about working in existing open source libraries, open a new issue!

First you should tell git your name and email (You can set specific ones for different repositories if you wish.). So if you're Scott Hanselman, you'd do it like this:

git config --global user.name "Scott Hanselman"
git config --global user.email [email protected]

If you want to set up a default editor you can set it using:

git config --global core.editor vim

To see what configuration settings you have:

git config --list

To clone this respository, click the green clone or download button above, pick HTTPS or SSH and copy the link. For HTTPS you can just add .git to the URL https://github.com/intelsdi-x/snap.git.

After copying the link, go to the path on your own computer that you want to clone this to. For organization it is more clear when there are separate directories for different repo owners.

Say you want to make changes on a branch other than master. This is common when wanting to separate different changes. If you want to have the exact

• git fetch: fetches the changes, but doesn't merge them
• git pull: does git fetch and git merge. This results in an extra commit.
• git pull --rebase: leaves your commits in a straight line without branches

Click the button at the top that says "Issues" and then the green button to the right.

Click the button at the top that says "Pull Requests" and then the green button to the right. If the pull request (PR) is to fix an existing issue, you can reference it by #somenumber, e.g. #2. It's common to say "Fixes #somenumber" so when the PR is merged, it closes the corresponding issue.

Tip: Include the issue the PR fixes in the commit message and have descriptive messages.

Great websites for people who are new to coding/contributing to open source:

• Code Newbie
• Get involved in tech
• First timers only
• Your first PR

• Official git documentation
• GitHub's Hello-World
• Brent Beer's OSCON talk: Everything I wish I knew when I started using GitHub
• SWDB-2015 Git and GitHub tutorial
• Start Learning Git and GitHub Today with Self-Paced Training

• Course from egghead.io: How to Contribute to an Open Source Project on GitHub