Need advice about which tool to choose?Ask the StackShare community!
GitHub vs Gitblit: What are the differences?
Introduction
GitHub and Gitblit are both platforms that are used for version control and collaboration on software development projects. While they have some similarities, there are also key differences between them that are worth noting.
Hosting Options: GitHub is a web-based hosting service that allows users to store and manage their repositories online. Gitblit, on the other hand, is a standalone application that can be run on a server or accessed through a web browser. While GitHub offers a cloud-based solution, Gitblit provides more flexibility by allowing users to host their repositories on their own infrastructure.
User Interface: GitHub has a user-friendly and visually appealing interface that offers a wide range of features such as issue tracking, pull requests, and project boards. Gitblit, on the other hand, has a simpler and more minimalistic interface that focuses primarily on the core functionalities of version control. While GitHub offers a more comprehensive and feature-rich interface, Gitblit provides a streamlined experience for users who prefer a more lightweight and efficient workflow.
Access Control: GitHub provides robust access control mechanisms that allow users to define fine-grained permissions for their repositories. Users can specify who can view, clone, push, and merge changes to their repositories. Gitblit also offers access control features, but they are more limited compared to GitHub. Gitblit allows users to define access control rules based on user roles, but the flexibility and granularity provided by GitHub are unmatched.
Integration with Third-party Services: GitHub offers seamless integration with a wide range of third-party services such as CI/CD tools, code review tools, and project management platforms. This integration allows users to automate workflows and enhance their development process. While Gitblit does support some integrations, it is more limited in terms of the number and variety of integrations available. GitHub's extensive ecosystem of integrations makes it a preferred choice for teams looking to streamline their development workflow.
Community and Collaboration: GitHub has a vibrant community of developers where users can discover and contribute to open-source projects. It provides features such as pull requests and issue tracking that facilitate collaboration and communication between team members. Gitblit, on the other hand, is more suited for smaller teams or organizations where collaboration is limited to a few individuals. While Gitblit does support collaborative features such as code reviews and branch merging, it lacks the extensive collaboration tools offered by GitHub.
Pricing: GitHub offers both free and paid plans, with the free plan providing access to basic features and limited storage. The paid plans offer additional storage, advanced features, and enhanced support. Gitblit, on the other hand, is an open-source software that is available for free. Users can install Gitblit on their own infrastructure without any additional costs. Gitblit's free and open-source nature makes it a cost-effective solution for organizations that want to have full control over their repositories.
In summary, GitHub offers a cloud-based hosting service with a feature-rich interface, extensive integration options, and a vibrant community, making it ideal for large teams and open-source projects. Gitblit, on the other hand, provides a lightweight and customizable solution that is more suited for smaller teams or organizations that want to host their repositories on their own infrastructure.
Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.
Now I want advice on below.
- Is it a good idea to migrate from Bitbucket to AWS Codecommit?
- If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
Hi Kavita. It would be useful to explain in a bit more detail the integration to Jira you would like to achieve. Some of the Jira plugins will work with any git repository, regardless if its github/bitbucket/gitlab.
Both of us are far more familiar with GitHub than Gitlab, and so for our first big project together decided to go with what we know here instead of figuring out something new (there are so many new things we need to figure out, might as well reduce the number of optionally new things, lol). We aren't currently taking advantage of GitHub Actions or very many other built-in features (besides Dependabot) but luckily it integrates very well with the other services we're using.
I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.
I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.
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?
Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.
SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.
As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?
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.
Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.
Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!
At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.
Pros of Gitblit
- Fast and fulfill just the features I need1
- Better user & group management1
- Free1
- Easy to setup. Runs on OSX1
- Windows authentication is supported0
- Run on Windows0
Pros of GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup867
- Issue tracker504
- Great community486
- Remote team collaboration482
- Great way to share451
- Pull request and features planning442
- Just works147
- Integrated in many tools132
- Free Public Repos121
- Github Gists116
- Github pages112
- Easy to find repos83
- Open source62
- It's free60
- Easy to find projects60
- Network effect56
- Extensive API49
- Organizations43
- Branching42
- Developer Profiles34
- Git Powered Wikis32
- Great for collaboration30
- It's fun24
- Clean interface and good integrations23
- Community SDK involvement22
- Learn from others source code20
- Because: Git16
- It integrates directly with Azure14
- Newsfeed10
- Standard in Open Source collab10
- Fast8
- It integrates directly with Hipchat8
- Beautiful user experience8
- Easy to discover new code libraries7
- Smooth integration6
- Cloud SCM6
- Nice API6
- Graphs6
- Integrations6
- It's awesome6
- Quick Onboarding5
- Remarkable uptime5
- CI Integration5
- Hands down best online Git service available5
- Reliable5
- Free HTML hosting4
- Version Control4
- Simple but powerful4
- Unlimited Public Repos at no cost4
- Security options4
- Loved by developers4
- Uses GIT4
- Easy to use and collaborate with others4
- IAM3
- Nice to use3
- Ci3
- Easy deployment via SSH3
- Good tools support2
- Leads the copycats2
- Free private repos2
- Free HTML hostings2
- Easy and efficient maintainance of the projects2
- Beautiful2
- Never dethroned2
- IAM integration2
- Very Easy to Use2
- Easy to use2
- All in one development service2
- Self Hosted2
- Issues tracker2
- Easy source control and everything is backed up2
- Profound1
Sign up to add or upvote prosMake informed product decisions
Cons of Gitblit
- Confusing UI2
- Squash and Merge is not supported0
- No active development0
- No code review functionality0
- No Pull Requests0
Cons of GitHub
- Owned by micrcosoft53
- Expensive for lone developers that want private repos37
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos8
- Limited featureset for issue management3
- GitHub Packages does not support SNAPSHOT versions2
- Does not have a graph for showing history like git lens2
- No multilingual interface1
- Takes a long time to commit1
- Expensive1