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

Gitea

235
387
+ 1
111
GitHub

232K
197.6K
+ 1
10.2K
Add tool

Gitea vs GitHub: What are the differences?

What is Gitea? A painless self-hosted Git service. Gitea is a community managed lightweight code hosting solution written in Go. It published under the MIT license.

What is GitHub? Powerful collaboration, review, and code management for open source and private development projects. 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.

Gitea and GitHub can be categorized as "Code Collaboration & Version Control" tools.

"Self-hosted" is the top reason why over 8 developers like Gitea, while over 1750 developers mention "Open source friendly" as the leading cause for choosing GitHub.

Gitea is an open source tool with 14.7K GitHub stars and 1.6K GitHub forks. Here's a link to Gitea's open source repository on GitHub.

Airbnb, Netflix, and Medium are some of the popular companies that use GitHub, whereas Gitea is used by osu! Ripple, LunchBadger, and PlayNet. GitHub has a broader approval, being mentioned in 4707 company stacks & 6088 developers stacks; compared to Gitea, which is listed in 8 company stacks and 10 developer stacks.

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 · 158K 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 · 180.3K 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 · 305.4K 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 · 484.8K 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
  • 22
    Self-hosted
  • 15
    Lightweight
  • 14
    Free
  • 11
    Simple
  • 9
    Multiple code maintainers
  • 8
    Easy Setup
  • 6
    Pull requests and code reviews
  • 5
    Written in Go
  • 5
    Squash and Merge is supported
  • 5
    Import existing git repositories
  • 4
    Nice gui
  • 3
    Run in Raspberry Pi
  • 2
    LDAP Support
  • 2
    Community-fork of Gogs
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.2K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 864
    Easy setup
  • 502
    Issue tracker
  • 484
    Great community
  • 480
    Remote team collaboration
  • 449
    Great way to share
  • 440
    Pull request and features planning
  • 144
    Just works
  • 131
    Integrated in many tools
  • 118
    Free Public Repos
  • 114
    Github Gists
  • 109
    Github pages
  • 82
    Easy to find repos
  • 61
    Open source
  • 59
    It's free
  • 59
    Easy to find projects
  • 56
    Network effect
  • 48
    Extensive API
  • 42
    Organizations
  • 41
    Branching
  • 33
    Developer Profiles
  • 32
    Git Powered Wikis
  • 29
    Great for collaboration
  • 23
    It's fun
  • 22
    Community SDK involvement
  • 22
    Clean interface and good integrations
  • 19
    Learn from others source code
  • 15
    Because: Git
  • 14
    It integrates directly with Azure
  • 9
    Standard in Open Source collab
  • 9
    Newsfeed
  • 8
    It integrates directly with Hipchat
  • 7
    Fast
  • 7
    Beautiful user experience
  • 6
    Cloud SCM
  • 6
    Easy to discover new code libraries
  • 5
    Smooth integration
  • 5
    It's awesome
  • 5
    Integrations
  • 5
    Graphs
  • 5
    Nice API
  • 4
    Quick Onboarding
  • 4
    Remarkable uptime
  • 4
    Hands down best online Git service available
  • 4
    CI Integration
  • 4
    Reliable
  • 3
    Loved by developers
  • 3
    Free HTML hosting
  • 3
    Security options
  • 3
    Simple but powerful
  • 3
    Uses GIT
  • 3
    Unlimited Public Repos at no cost
  • 3
    Version Control
  • 3
    Easy to use and collaborate with others
  • 2
    Nice to use
  • 2
    IAM
  • 2
    Ci
  • 1
    Easy and efficient maintainance of the projects
  • 1
    Good tools support
  • 1
    Beautiful
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    IAM integration
  • 1
    Issues tracker
  • 1
    Very Easy to Use
  • 1
    Easy deployment via SSH
  • 1
    Free private repos
  • 0
    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
  • 51
    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
    Have to use a token for the package registry
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Gitea?

Gitea is a community managed lightweight code hosting solution written in Go. 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!

Jobs that mention Gitea and GitHub as a desired skillset
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
2132
GitHubOptimizelySegment+3
2
1086
Mar 18 2020 at 9:12AM

LaunchDarkly

GitHubLaunchDarkly+2
6
1028
JavaScriptGitHubReact+12
5
3832
GitHubDockerReact+17
35
33386
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