![]() ![]() If this box is unchecked, anyone can see your 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. 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. 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).Ĭlick the Commit button at the top to commit the file. In the message box, enter "Initial commit."Ĭlick the Commit button under the box. ![]() 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.įrom 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.įrom the dialog box that appears, your next step depends on whether you are using Git or Mercurial: Your new file is now committed to the project history. Git–Under the Push? column, select the main 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. ![]()
0 Comments
Leave a Reply. |