![]() In the "Propose changes" box, write a commit message that describes your changes. In the editor, write a bit about yourself. Under the readme-edits branch you created, click the README.md file. Commit messages capture the history of your changes so that other contributors can understand what you’ve done and why. Each commit has an associated commit message, which is a description explaining why a particular change was made. ![]() On GitHub, saved changes are called commits. You can make and save changes to the files in your repository. ![]() When you created a new branch in the previous step, GitHub brought you to the code page for your new readme-edits branch, which is a copy of main. Next you'll add changes to the new branch. Now you have two branches, main and readme-edits. Type a branch name, readme-edits, into the text box.Ĭlick Create branch: readme-edits from main. Create a branchĬlick the Code tab of your hello-world repository.Ībove the file list, click the dropdown menu that says main. When a change is ready, they merge their branch into main. Here at GitHub, our developers, writers, and designers use branches for keeping bug fixes and feature work separate from our main (production) branch. Have you ever saved different versions of a file? Something like:īranches accomplish similar goals in GitHub repositories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |