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

Gitea

289
442
+ 1
118
GitHub

280.6K
244.9K
+ 1
10.3K
Add tool

GitHub vs Gitea: What are the differences?

Introduction: GitHub and Gitea are both web-based hosting services for version control using Git. While they have similar functionalities, there are key differences between the two platforms that set them apart from each other.

  1. User Interface and User Experience: GitHub provides a more polished and user-friendly interface compared to Gitea. It offers a visually pleasing and intuitive design, making it easier for users to navigate and understand its features. On the other hand, Gitea has a simpler and more minimalist interface, which may appeal to users who prefer a more streamlined experience.

  2. Hosting Options: GitHub is a cloud-based service, meaning that it hosts repositories on its servers, which allows for easy collaboration and access from anywhere with an internet connection. Gitea, on the other hand, can be self-hosted, allowing organizations to have more control over their repositories and data.

  3. Community and Integrations: GitHub has a larger and more vibrant community compared to Gitea, making it a hub for open-source collaboration. It offers a wide range of integrations with popular development tools and services, such as CI/CD pipelines and project management tools. While Gitea also has a community and integrations, they may not be as extensive or well-established as those on GitHub.

  4. Scalability and Performance: GitHub is designed to handle a massive amount of traffic and repositories, making it suitable for large-scale projects and organizations. It has robust infrastructure and resources to ensure high availability and performance. Gitea, being a self-hosted solution, may not have the same level of scalability and performance as GitHub, as it depends on the hardware and resources allocated to it by the organization hosting it.

  5. Pricing: GitHub offers different pricing plans, including a free tier for public repositories and paid plans for private repositories. It also offers additional features and support depending on the plan. Gitea, being an open-source project, is free to use and has no associated costs. However, organizations opting for a self-hosted solution need to consider the costs of hardware, maintenance, and support.

  6. Customization and Flexibility: Gitea offers more customization options compared to GitHub. With Gitea, organizations can tailor the platform to their specific requirements and preferences. It allows for the installation of plugins and extensions, enabling users to extend its functionality. GitHub, while it provides some customization options, may have limitations due to its cloud-based nature and standard configuration.

In summary, GitHub offers a more user-friendly interface, extensive community and integrations, scalability, pricing options, and customization options. Gitea, on the other hand, provides self-hosting capabilities, simplicity, and flexibility for organizations that prefer more control over their repositories and infrastructure.

Advice on Gitea 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 · 328.1K 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 Gitea and GitHub
Phillip Manwaring
Developer at Coach Align · | 17 upvotes · 357K 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 · 519.5K 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 · 673K 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 Gitea
Pros of GitHub
  • 23
    Self-hosted
  • 16
    Lightweight
  • 15
    Free
  • 12
    Simple
  • 9
    Easy Setup
  • 9
    Multiple code maintainers
  • 6
    Pull requests and code reviews
  • 5
    Import existing git repositories
  • 5
    Squash and Merge is supported
  • 5
    Written in Go
  • 4
    Nice gui
  • 3
    Run in Raspberry Pi
  • 2
    Community-fork of Gogs
  • 2
    LDAP Support
  • 1
    Richable Packages
  • 1
    Gitea Actions(Github compatible)
  • 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
  • 483
    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
    Standard in Open Source collab
  • 10
    Newsfeed
  • 8
    It integrates directly with Hipchat
  • 8
    Fast
  • 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
    Reliable
  • 5
    Remarkable uptime
  • 5
    CI Integration
  • 5
    Hands down best online Git service available
  • 4
    Uses GIT
  • 4
    Version Control
  • 4
    Simple but powerful
  • 4
    Unlimited Public Repos at no cost
  • 4
    Free HTML hosting
  • 4
    Security options
  • 4
    Loved by developers
  • 4
    Easy to use and collaborate with others
  • 3
    Ci
  • 3
    IAM
  • 3
    Nice to use
  • 3
    Easy deployment via SSH
  • 2
    Easy to use
  • 2
    Leads the copycats
  • 2
    All in one development service
  • 2
    Free private repos
  • 2
    Free HTML hostings
  • 2
    Easy and efficient maintainance of the projects
  • 2
    Beautiful
  • 2
    Easy source control and everything is backed up
  • 2
    IAM integration
  • 2
    Very Easy to Use
  • 2
    Good tools support
  • 2
    Issues tracker
  • 2
    Never dethroned
  • 2
    Self Hosted
  • 1
    Dasf
  • 1
    Profound

Sign up to add or upvote prosMake informed product decisions

Cons of Gitea
Cons of GitHub
  • 3
    Community-fork of Gogs
  • 0
    Easy Windows authentication is not supported
  • 54
    Owned by micrcosoft
  • 38
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 9
    Only 3 collaborators for private repos
  • 4
    Limited featureset for issue management
  • 3
    Does not have a graph for showing history like git lens
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit
  • 1
    Expensive

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is 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.

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 Gitea?
What companies use GitHub?
See which teams inside your own company are using Gitea 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 Gitea?
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
2372
GitHubOptimizelySegment+3
2
1180
Mar 18 2020 at 9:12AM

LaunchDarkly

GitHubLaunchDarkly+2
7
1116
JavaScriptGitHubReact+12
5
4145
GitHubDockerReact+17
41
36578
What are some alternatives to Gitea and GitHub?
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.
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.
Phabricator
Phabricator is a collection of open source web applications that help software companies build better software.
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.
GitBucket
GitBucket provides a Github-like UI and features such as Git repository hosting via HTTP and SSH, repository viewer, issues, wiki and pull request.
See all alternatives