Bitbucket vs Git: What are the differences?
Developers describe Bitbucket as "One place to plan projects, collaborate on code, test and deploy, all with free private repositories". Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. On the other hand, Git is detailed as "Fast, scalable, distributed revision control system". Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Bitbucket belongs to "Code Collaboration & Version Control" category of the tech stack, while Git can be primarily classified under "Version Control System".
"Free private repos", "Simple setup" and "Nice ui and tools" are the key factors why developers consider Bitbucket; whereas "Distributed version control system", "Efficient branching and merging" and "Fast" are the primary reasons why Git is favored.
Git is an open source tool with 28.2K GitHub stars and 16.3K GitHub forks. Here's a link to Git's open source repository on GitHub.
According to the StackShare community, Git has a broader approval, being mentioned in 3934 company stacks & 4787 developers stacks; compared to Bitbucket, which is listed in 1750 company stacks and 1494 developer stacks.
Do you review your Pull/Merge Request before assigning Reviewers?
If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:
- Pick the correct target branch
- Make Drafts explicit
- Name things properly
- Ask help for tools
- Remove the noise
- Fetch necessary data
- Understand Mergeability
- Pass the message
- Add screenshots
- Be found in the future
- Comment inline in your changes
Read the blog post for more detailed explanation for each item :D
What else do you review before asking for code review?
One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but
git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.
It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.