Cloud
Data Center 7.2
Versions

Git resources

Get started with Bitbucket Server

On this page

In this section

Related content

Still need help?

The Atlassian Community is here for you.

Ask the community

Get Git

See Installing and upgrading Git

Learning Git

Git Tutorials and Training

Basic Git commands

Getting started

One "gotcha" when starting with Git is the way in which it pushes branches by default. On older versions of Git, pushing without arguments would push all branches that have the same name both locally and remotely. This can result in unexpected behavior if you have old branches that complain when the remote branch is updated. It can even be quite dangerous if you do a force push and it reverts changes on the server. You can see the current value by running:

git config push.default

If this value is blank or 'matching', it is our recommendation that you reconfigure it to use 'upstream'.

git config --global push.default upstream

There has been some discussion around changing the default behavior of Git.

Git cheat sheets and other resources

http://rogerdudler.github.com/git-guide/

http://byte.kde.org/~zrusin/git/git-cheat-sheet-medium.png

http://nvie.com/posts/a-successful-git-branching-model/

http://zrusin.blogspot.com.au/2007/09/git-cheat-sheet.html

http://ndpsoftware.com/git-cheatsheet.html#loc=workspace;

http://blog.fournova.com/2011/06/git-cheat-sheet/

http://jan-krueger.net/development/git-cheat-sheet-extended-edition

Git .mailmap

The Git .mailmap feature is useful locally, and in Bitbucket Server repositories, to map multiple commit identities to the one Bitbucket Server user – this can be used to tidy up your Git histories.

The Git documentation for .mailmap has configuration details (see the "MAPPING AUTHORS" section).

Last modified on May 26, 2020

Was this helpful?

Yes
No
Provide feedback about this article

In this section

Related content

Powered by Confluence and Scroll Viewport.