Your first contribution #2
Introduction to GitHub flow
Now that you're familiar with issues, let's use this issue to track your path to your first contribution.
People use different workflows to contribute to software projects, but the simplest and most effective way to contribute on GitHub is the GitHub flow.
Read below for next steps
Step 4: Create a branch
Let’s complete the first step of the GitHub flow: creating a branch
Creating a branch
Creating a branch
You just learned how to create a branch—the first step in the GitHub flow.
Branches are an important part of the GitHub flow because they allow us to separate our work from the
Tips for using branches
A single project can have hundreds of branches, each suggesting a new change to the
The best way to keep branches organized with a team is to keep them concise and short-lived. In other words, a single branch should represent a single new feature or bug fix. This reduces confusion among contributors when branches are only active for a few days before they’re merged
Step 5: Commit a file
Creating a branch allows you to make modifications to your project without changing the deployed
When you’re finished creating or making changes to a file on GitHub, scroll to the bottom of the page. Then find the "Commit new file" section.
In the first field, type a commit message. The commit message should briefly tell contributors about the changes you are introducing to the file.
Rules to live by for commit messages:
Step 6: Open a pull request
Nice work making that commit
Now that you’ve created a commit, it’s time to share your proposed change through a pull request! Where issues encourage discussion with other contributors and collaborators on a project, pull requests help you share your changes, receive feedback on them, and iterate on them until they’re perfect!
What is a pull request?
Let’s think back to the GitHub flow again. You have created a branch, added a file, and committed the file to your branch. Now it’s time to collaborate on your file with other students taking this class. This collaboration happens in a pull request. Check out this video to learn more:
This pull request is going to keep the changes you just made on your branch and propose applying them to the