Go to your BitbucketStationSupplies repository in Bitbucket. Mercurial–Everything is automatic, so all you have to do is click OK. Git–Under the Push? column, select the main branch to indicate that you are pushing that branch to origin and click OK. 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. 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.Git config -global user.Do the following to create your repository: While I’m in the Git username neighborhood, I’ll also add that you can view your Git email address with this command:Īnd you can change your Git email address like this: I just looked it up, and you should be able to change your Git username on a per-project basis like this, without the -global option:
You can also have a different username on a per-project basis. I just did that on my test system, and it seems to work fine.Īgain, it’s important to note that this is your “global” username. Alexander"Īnother way to change it is to edit the Git config file in your HOME directory and change it there: You can change your Git username like this: You can also have a different username on a per-project basis (but I haven’t used that yet).
It’s important to note that this is your “global” Git username. My file on my current test system looks like this:
There are at least three ways to show your Git username:Īnother way to show your Git username is with this git config command:įinally, you can also see your Git username in the Git configuration file in your HOME directory on Unix systems, i.e., this file:
#GIT BASH ON MAC HOW TO#
Git user FAQ: How do I show or change my Git username (or email address)? How to show your Git username Using an ad blocker? just a $2 donation at will help keep this site running
0 kommentar(er)
