Comments (3)
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 master
branch. In other words, everyone's work is safe while you contribute.
Tips for using branches
A single project can have hundreds of branches, each suggesting a new change to the master
branch.
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 definition into the master
branch.
⌨️ Activity: Your first branch
- Open your preferred command line interface, which we'll call your shell from now on.
- Clone this repository:
git clone https://github.com/dvanic/github-slideshow.git
- Navigate to the repository in your shell:
cd github-slideshow
- Create a branch, use whatever name you like:
git branch <BRANCH-NAME>
- Push the branch to GitHub:
git push --set-upstream origin <BRANCH-NAME>
Return to this issue for my response
from github-slideshow.
Step 5: Commit a file
🎉 You created a branch!
Creating a branch allows you to make modifications to your project without changing the deployed master
branch. Now that you have a branch, it’s time to create a file and make your first commit!
Commits 101
Commits 101
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:
- Don’t end your commit message with a period.
- Keep your commit messages to 50 characters or less. Add extra detail in the extended description window if necessary. This is located just below the subject line.
- Use active voice. For example, "add" instead of "added" and "merge" instead of "merged".
- Think of your commit as expressing intent to introduce a change.
⌨️ Activity: Your first commit
The following steps will guide you through the process of committing a change on GitHub.
- Check out to your branch:
git checkout testme
- Create a new file named
_posts/0000-01-02-dvanic.md
. - Add the following content to your file:
--- layout: slide title: "Welcome to our second slide!" --- Your text Use the left arrow to go back!
- Stage your new file:
git add _posts/0000-01-02-dvanic.md
- After adding the text, commit the change and a commit message, check out the Commits 101 drop-down, just above these instructions:
git commit -m "<YOUR-MESSAGE>"
- Push your new commit to GitHub:
git push
Return to this issue for my response
from github-slideshow.
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?
Pull requests
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:
📺 Video: Introduction to pull requests
This pull request is going to keep the changes you just made on your branch and propose applying them to the master
branch.
⌨️ Activity: Create a pull request
- From the "Pull requests" tab, click New pull request
- In the "base:" drop-down menu, make sure the "master" branch is selected
- In the "compare:" drop-down menu, select "refs/heads/testme"
- Click Create pull request
- When you’ve selected your branch, enter a title for your pull request. For example
Add dvanic's file
- The next field helps you provide a description of the changes you made. Feel free to add a description of what you’ve accomplished so far. As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request
- Click Create pull request
Look for my next response in your pull request
from github-slideshow.
Related Issues (2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from github-slideshow.