クラウド
Data Center 6.7
バージョン

Git resources

Get started with Bitbucket Server

このページの内容

このセクションの項目

関連コンテンツ

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

Get Git

See Installing and upgrading Git

Learning Git

Git チュートリアルとトレーニング

基本的な Git コマンド

入門ガイド

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).

最終更新日 2019 年 11 月 5 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する

このセクションの項目

関連コンテンツ

Powered by Confluence and Scroll Viewport.