Bitbucket vs GitKraken: What are the differences?
Bitbucket: 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; GitKraken: Git GUI Client for Windows Mac and Linux built on Electron. The downright luxurious Git client for Windows, Mac and Linux. Cross-platform, 100% standalone, and free.
Bitbucket can be classified as a tool in the "Code Collaboration & Version Control" category, while GitKraken is grouped under "Source Code Management Desktop Apps".
"Free private repos" is the primary reason why developers consider Bitbucket over the competitors, whereas "Dark theme" was stated as the key factor in picking GitKraken.
According to the StackShare community, Bitbucket has a broader approval, being mentioned in 1750 company stacks & 1493 developers stacks; compared to GitKraken, which is listed in 43 company stacks and 38 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.