For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. This makes it easy to revert your changes if you decide to take a different approach. Ideally, each commit contains an isolated, complete change. For example, fix typo or increase rate limit. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. Your changes will not end up on the default branch until you merge your branch.Ĭommit and push your changes to your branch. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your branch is a safe place to make changes. For more information, see " Creating new files", " Editing files", " Renaming a file", " Moving a file to a new location", or " Deleting files in a repository". On your branch, make any desired changes to the repository. Additionally, you give collaborators a chance to review your work. For more information, see " Creating and deleting branches within your repository."īy creating a branch, you create a space to work without affecting the default branch. For example, increase-test-timeout or add-code-of-conduct.
A short, descriptive branch name enables your collaborators to see ongoing work at a glance. Create a branchĬreate a branch in your repository. Tip: You can complete all steps of GitHub flow through GitHub web interface, command line and GitHub CLI, or GitHub Desktop.
0 kommentar(er)
