In the message box, enter "Initial commit."Ĭlick the Commit button under the box. From the options menu of the supplies.txt file, select Stage file (for a Git repository) or Add file (for a Mercurial repository).Ĭlick the Commit button at the top to commit the file. Now is the point where you prepare a snapshot of the changes before committing them to the official history. Save the file as supplies.txt to the bitbucketstationsupplies directory on your local system. The supplies.txt file now appears in Sourcetree since you created it in your local repository. Use a text editor to add the following three lines: If you aren't sure which one to go with, keep Git as your option.Ĭlick Create repository. Bitbucket creates your repository and displays its Source page.ĭouble-click the bitbucketstationsupplies repository in Sourcetree and notice that there is nothing to commit from your local repository to the remote repository. Include a README? -If you recently created your account, this defaults to a tutorial README. For the purposes of this tutorial, pick either of the Yes options, that way you'll start out with a file.įrom Version control system, you can choose either Git or Mercurial. If this box is unchecked, anyone can see your repository. Keep the rest of the options as is unless you want to change them:Īccess level -Leave the This is a private repository box checked. A private repository is only visible to you and those with access. For example, if the user the_best has a repository called awesome_repo, the URL for that repository would be. Bitbucket uses this Name in the URL of the repository. With the exception of the Repository type, everything you enter on this page you can later change.Įnter BitbucketStationSupplies for the Name field. Take some time to review the dialog's contents. Bitbucket displays the Create a new repository page. From Bitbucket, click the + icon in the global sidebar and select Repository.By default, GitHub Desktop uses main as the default branch name in any new repositories you create.Do the following to create your repository: GitHub Desktop also allows you to change the default branch name that you would like to use when creating new repositories. If the email address that has been set in your Git configuration does not match an email address associated with the GitHub account you are currently logged in to, GitHub Desktop will show a warning prior to committing. This is useful when you need to use a separate work email address for a specific repository.
GitHub Desktop also allows you to set a different name and email address for an individual repository. If your name and email address have already been set in the global Git configuration for your computer, GitHub Desktop will detect and use those values. GitHub Desktop allows you to set the name and email address you would like associated with the commits you make in your repositories. GitHub Desktop uses your local Git configuration settings and provides the option to configure some of these settings, such as the global author information and the default branch that is used when creating a new repository. About Git configuration for GitHub Desktop