Tutorial: Work with Bitbucket Server
Tutorials
On this page
In this section
Related content
- How to define a default merge strategy per Project
- Remote merge is not happening in Bitbucket Server
- Merge a pull request
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Cascading merge
- Keeping forks synchronized
- Commits missing from Pull Request merge on target branch
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Bitbucket Server is unable to create the merge diff for pull requests
Teams in Space is a fictional company created by Atlassian that specializes in space travel for teams.
Welcome to the Teams in Space web team! You are joining us as a Bitbucket Data Center and Server web developer, and your first assignment is to update our company website to include a link to our Moon Itinerary so that our customers know what to expect on their day trip to the Moon.
Here's what you'll accomplish by the end of this tutorial:
- Set up Sourcetree to work with Bitbucket
- Create a personal repository for the tutorial
- Clone your repository and manage files locally
- Commit and push changes
For this tutorial we'll be using Sourcetree, a desktop Git client with a graphical interface, to work with Bitbucket. If you're already comfortable using Git from the command line we'll also include the Git command equivalent.
Time needed
5-10 minutes
Audience
You're new to working with Bitbucket
Prerequisites
- Bitbucket is installed
- You have login credentials
- You have a project and repo
Here's what the final version of the HTML page will look like when you're finished (and we've got all the files you need to get this end result).
In this section
Related content
- How to define a default merge strategy per Project
- Remote merge is not happening in Bitbucket Server
- Merge a pull request
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Cascading merge
- Keeping forks synchronized
- Commits missing from Pull Request merge on target branch
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Bitbucket Server is unable to create the merge diff for pull requests