Git resources
Get started with Bitbucket Server
このページの内容
関連コンテンツ
- Unable to merge a pull request when using the Required Builds merge check in Bitbucket Data Center
- Missing commits in Bitbucket after a filesystem migration
- Changed file list missing from commit details after upgrade to version 3
- Repository has invalid reflog entry
- Missing Pull Requests in Bitbucket Server
- How to diagnose/debug issues with Pull Request rescoping in Bitbucket Data Center
- Recent commits are not visible in pull-requests for all repositories in Bitbucket 8.x
- Bitbucket Server REST API for merging Pull Request fails
- After the git version upgrade, Bitbucket Server shows the "CRLF will be replaced by LF" error during the commit in Bitbucket UI.
- Recent commits are not visible in pull-requests for all repositories in Bitbucket 8.x
Get Git
Learning 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 .mailmap
The Git .mailmap
feature is useful locally, and in Bitbucket Data Center and Server repositories, to map multiple commit identities to the one Bitbucket user – this can be used to tidy up your Git histories.
The Git documentation for .mailmap
has configuration details (see the "MAPPING AUTHORS" section).
関連コンテンツ
- Unable to merge a pull request when using the Required Builds merge check in Bitbucket Data Center
- Missing commits in Bitbucket after a filesystem migration
- Changed file list missing from commit details after upgrade to version 3
- Repository has invalid reflog entry
- Missing Pull Requests in Bitbucket Server
- How to diagnose/debug issues with Pull Request rescoping in Bitbucket Data Center
- Recent commits are not visible in pull-requests for all repositories in Bitbucket 8.x
- Bitbucket Server REST API for merging Pull Request fails
- After the git version upgrade, Bitbucket Server shows the "CRLF will be replaced by LF" error during the commit in Bitbucket UI.
- Recent commits are not visible in pull-requests for all repositories in Bitbucket 8.x