Double-click the bitbucketstationsupplies repository in Sourcetree and notice that there is nothing to commit from your local repository to the remote repository.



Use a text editor to add the following three lines:

space ice

cream nerf

darts telescope light shield

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.



Now is the point where you prepare a snapshot of the changes before committing them to the official history. From the options menu of the supplies.txt file, select Stage file (for a Git repository) or Add file (for a Mercurial repository).





Click the Commit button at the top to commit the file.

In the message box, enter "Initial commit."



Click the Commit button under the box. Your new file is now committed to the project history.



Up until this point, everything you have done is on your local system and is invisible to your Bitbucket repository until you push those changes to your remote Bitbucket repository.

From Sourcetree, click the Push button to push your committed changes. Pushing lets you move one or more commits to another repository, which serves as a convenient way to publish contributions.



From the dialog box that appears, your next step depends on whether you are using Git or Mercurial: Git–Under the Push? column, select the master branch to indicate that you are pushing that branch to origin and click OK .



Mercurial–Everything is automatic, so all you have to do is click OK.