Need advice about which tool to choose?Ask the StackShare community!

Gitblit

19
55
+ 1
4
GitHub

279K
243.3K
+ 1
10.3K
Add tool

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Advice on Gitblit and GitHub

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.

  1. Is it a good idea to migrate from Bitbucket to AWS Codecommit?
  2. 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?
See more
Replies (1)
Sinisha Mihajlovski
Design Lead | Senior Software Developer · | 1 upvotes · 311.7K views
Recommends

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.

See more
Decisions about Gitblit and GitHub
Phillip Manwaring
Developer at Coach Align · | 17 upvotes · 340.7K views

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.

See more
Elmar Wouters
CEO, Managing Director at Wouters Media · | 7 upvotes · 501.7K views

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.

See more
Weverton Timoteo

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?

See more
Weverton Timoteo

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?

See more
Weverton Timoteo

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.

See more
Kamaleshwar BN
Senior Software Engineer at Pulley · | 8 upvotes · 664.6K views

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.

See more

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!

See more
Nazar Atamaniuk
Shared insights
on
DeployPlaceDeployPlaceGitHubGitHubGitLabGitLab

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Gitblit
Pros of GitHub
  • 1
    Fast and fulfill just the features I need
  • 1
    Better user & group management
  • 1
    Free
  • 1
    Easy to setup. Runs on OSX
  • 0
    Windows authentication is supported
  • 0
    Run on Windows
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.3K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 867
    Easy setup
  • 504
    Issue tracker
  • 486
    Great community
  • 482
    Remote team collaboration
  • 451
    Great way to share
  • 442
    Pull request and features planning
  • 147
    Just works
  • 132
    Integrated in many tools
  • 121
    Free Public Repos
  • 116
    Github Gists
  • 112
    Github pages
  • 83
    Easy to find repos
  • 62
    Open source
  • 60
    It's free
  • 60
    Easy to find projects
  • 56
    Network effect
  • 49
    Extensive API
  • 43
    Organizations
  • 42
    Branching
  • 34
    Developer Profiles
  • 32
    Git Powered Wikis
  • 30
    Great for collaboration
  • 24
    It's fun
  • 23
    Clean interface and good integrations
  • 22
    Community SDK involvement
  • 20
    Learn from others source code
  • 16
    Because: Git
  • 14
    It integrates directly with Azure
  • 10
    Newsfeed
  • 10
    Standard in Open Source collab
  • 8
    Fast
  • 8
    It integrates directly with Hipchat
  • 8
    Beautiful user experience
  • 7
    Easy to discover new code libraries
  • 6
    Smooth integration
  • 6
    Cloud SCM
  • 6
    Nice API
  • 6
    Graphs
  • 6
    Integrations
  • 6
    It's awesome
  • 5
    Quick Onboarding
  • 5
    Remarkable uptime
  • 5
    CI Integration
  • 5
    Hands down best online Git service available
  • 5
    Reliable
  • 4
    Free HTML hosting
  • 4
    Version Control
  • 4
    Simple but powerful
  • 4
    Unlimited Public Repos at no cost
  • 4
    Security options
  • 4
    Loved by developers
  • 4
    Uses GIT
  • 4
    Easy to use and collaborate with others
  • 3
    IAM
  • 3
    Nice to use
  • 3
    Ci
  • 3
    Easy deployment via SSH
  • 2
    Good tools support
  • 2
    Leads the copycats
  • 2
    Free private repos
  • 2
    Free HTML hostings
  • 2
    Easy and efficient maintainance of the projects
  • 2
    Beautiful
  • 2
    Never dethroned
  • 2
    IAM integration
  • 2
    Very Easy to Use
  • 2
    Easy to use
  • 2
    All in one development service
  • 2
    Self Hosted
  • 2
    Issues tracker
  • 2
    Easy source control and everything is backed up
  • 1
    Profound

Sign up to add or upvote prosMake informed product decisions

Cons of Gitblit
Cons of GitHub
  • 2
    Confusing UI
  • 0
    Squash and Merge is not supported
  • 0
    No active development
  • 0
    No code review functionality
  • 0
    No Pull Requests
  • 53
    Owned by micrcosoft
  • 37
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 8
    Only 3 collaborators for private repos
  • 3
    Limited featureset for issue management
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 2
    Does not have a graph for showing history like git lens
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit
  • 1
    Expensive

Sign up to add or upvote consMake informed product decisions

What is Gitblit?

Gitblit is an open source, pure Java Git solution for managing, viewing, and serving Git repositories. It can serve repositories over the GIT, HTTP, and SSH transports; it can authenticate against multiple providers; and it allows you to get up-and-running with an attractive, capable Git server in less than 5 minutes.

What is GitHub?

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Gitblit?
What companies use GitHub?
See which teams inside your own company are using Gitblit or GitHub.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Gitblit?
What tools integrate with GitHub?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Dec 8 2020 at 5:50PM

DigitalOcean

GitHubMySQLPostgreSQL+11
2
2361
GitHubOptimizelySegment+3
2
1177
Mar 18 2020 at 9:12AM

LaunchDarkly

GitHubLaunchDarkly+2
7
1110
JavaScriptGitHubReact+12
5
4137
GitHubDockerReact+17
40
36306
What are some alternatives to Gitblit and GitHub?
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
Gitolite
Gitolite allows you to setup git hosting on a central server, with fine-grained access control and many more powerful features. Gitolite is an access control layer on top of git.
Gogs
The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.
Bitbucket
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.
Gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.
See all alternatives