Arepository is usually used to organize a single project. Repositories can contain folders and files, images, videos, spreadsheets, and data sets – anything your project needs. We recommend including aREADME, or a file with information about your project. GitHub makes it easy to add one at the same time you create your new repository. 📁

Yourhello-CodeCosmers repository can be a place where you store ideas, resources, or even share and discuss things with others. 🤝

• To create a new repository 🌟

1. In the upper right corner, next to your avatar or identicon, clickand then selectNew repository. 📅
2. Name your repositoryhello-CodeCosmers. 🌐
3. Write a short description. 📝
4. SelectInitialize this repository with a README. 📂

🚀

ClickCreate repository. 🚀

Branching is the way to work on different versions of a repository at one time. 🔄

• By default, your repository has one branch namedmaster which is considered to be the definitive branch. We use branches to experiment and make edits before committing them tomaster. 🎨

• When you create a branch off themaster branch, you’re making a copy, or snapshot, ofmaster as it was at that point in time. If someone else made changes to themaster branch while you were working on your branch, you could pull in those updates. 🔄

• This diagram shows:

• Themaster branch 🌟

• A new branch calledfeature (because we’re doing ‘feature work’ on this branch) 🌟

• The journey thatfeature takes before it’s merged intomaster 🌟

🌿

Have you ever saved different versions of a file? Something like:

• story.txt 📖
• story-shreya-edit.txt ✏️
• story-shreya-edit-reviewed.txt 📝

Branches accomplish similar goals in GitHub repositories. 🌟

• Here at GitHub, our developers, writers, and designers use branches for keeping bug fixes and feature work separate from ourmaster (production) branch. When a change is ready, they merge their branch intomaster. 🤝

• To create a new branch 🌿

1. Go to your new repositoryhello-CodeCosmers. 🚀
2. Click the drop down at the top of the file list that saysbranch: master. 🌿
3. Type a branch name,readme-edits, into the new branch text box. 📝
4. Select the blueCreate branch box or hit “Enter” on your keyboard. 🚀

🌟

• Now you have two branches,master andreadme-edits. They look exactly the same, but not for long! Next, we’ll add our changes to the new branch. 🌟

• Bravo! Now, you’re on the code view for yourreadme-edits branch, which is a copy ofmaster. Let’s make some edits. 💻

• On GitHub, saved changes are calledcommits. Each commit has an associatedcommit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes, so other contributors can understand what you’ve done and why. 📜

• Make and commit changes 📝

• 1. Click theREADME.md file. 📖
• 2. Click thepencil icon in the upper right corner of the file view to edit. ✏️
• 3. In the editor, write a bit about yourself. 🤖
• 4. Write a commit message that describes your changes. 📝
• 5. ClickCommit changes button. 🚀

🌟

• These changes will be made to just the README file on yourreadme-edits branch, so now this branch contains content that’s different frommaster. 🌟

• Nice edits! Now that you have changes in a branch off ofmaster, you can open apull request. 🌟

• Pull Requests are the heart of collaboration on GitHub. When you open apull request, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests showdiffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red. 🌟

• As soon as you make a commit, you can open a pull request and start a discussion, even before the code is finished. 🌟

• By using GitHub’s@mention system in your pull request message, you can ask for feedback from specific people or teams, whether they’re down the hall or 10 time zones away. 🌟

You can even open pull requests in your own repository and merge them yourself. It’s a great way to learn the GitHub Flow before working on larger projects. 🌟

• Open a Pull Request for changes to the README 📜

Click on the image for a larger version 🌟

Step	Screenshot
Click thePull Request tab, then from the Pull Request page, click the greenNew pull request button.
In theExample Comparisons box, select the branch you made,readme-edits, to compare withmaster (the original).
Look over your changes in the diffs on the Compare page, make sure they’re what you want to submit.
When you’re satisfied that these are the changes you want to submit, click the big greenCreate Pull Request button.
Give your pull request a title and write a brief description of your changes.

• When you’re done with your message, clickCreate pull request! 🌟

Tip: You can useemoji anddrag and drop images and gifs onto comments and Pull Requests. 🌟

• In this final step, it’s time to bring your changes together – merging yourreadme-edits branch into themaster branch. 🌟

1. Click the greenMerge pull request button to merge the changes intomaster. 🔄
2. ClickConfirm merge. 🌟
3. Go ahead and delete the branch, since its changes have been incorporated, with theDelete branch button in the purple box. ❌

🌟