Atlassian Stash vs GitHub

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

Atlassian Stash

+ 1

+ 1
Add tool

Atlassian Stash vs GitHub: What are the differences?


In this article, we will explore the key differences between Atlassian Stash and GitHub. Both Stash and GitHub are popular version control systems used by software development teams to manage their code repositories. Understanding the differences between these two platforms can help organizations make an informed decision on which platform best suits their needs.

  1. Infrastructure: One major difference between Atlassian Stash and GitHub lies in the infrastructure they offer. Atlassian Stash is an on-premises solution that is hosted on a company's own servers. On the other hand, GitHub is a cloud-based platform, which means all the code repositories are hosted on GitHub's servers. This distinction in infrastructure has implications on factors such as security, scalability, and maintenance.

  2. Integration with Atlassian Tools: Stash, being an Atlassian product, seamlessly integrates with other Atlassian tools such as Jira, Confluence, and Bitbucket. This tight integration allows for seamless collaboration between different teams and streamlines the development workflow. GitHub, on the other hand, does not have the same level of integration with Atlassian tools out of the box, although there are some third-party integrations available.

  3. Pricing Model: The pricing models of Stash and GitHub also differ. Atlassian Stash follows a traditional license-based pricing model, where organizations purchase licenses based on the number of users or repositories. GitHub, on the other hand, offers a freemium model, where individuals and small teams can use the platform for free, with paid plans available for larger organizations or teams that require advanced features and enterprise-level support.

  4. Community and Ecosystem: GitHub has a significantly larger community and ecosystem compared to Atlassian Stash. Being one of the most popular version control systems, GitHub hosts a vast number of open-source projects, making it a go-to platform for developers to discover, collaborate, and contribute to projects. This extensive community also leads to a wider range of integrations and tools that are built specifically for GitHub, making it more versatile and extensible.

  5. Branching and Pull Request Workflows: While both Stash and GitHub support branching and pull request workflows, there are some differences in how they handle these processes. Stash offers a highly flexible and customizable branching model, allowing teams to define and enforce specific workflows based on their requirements. GitHub, on the other hand, provides a more streamlined and simplified approach to branching and pull requests, making it easier for beginners to get started.

  6. User Interface and User Experience: The user interface and user experience on Stash and GitHub also differ in various aspects. Stash has a more minimalistic and straightforward interface, which can be beneficial for users who prefer a clean and clutter-free interface. GitHub, on the other hand, has a more visually rich and feature-packed interface, which can be attractive for users who value extensive functionality and a visually appealing experience.

In summary, the key differences between Atlassian Stash and GitHub can be highlighted in terms of infrastructure (on-premises vs. cloud), integration with Atlassian tools, pricing models, community and ecosystem, branching and pull request workflows, and user interface/user experience. These differences ultimately shape the unique offerings and strengths of each platform, allowing organizations to choose the one that aligns better with their specific requirements and preferences.

Decisions about Atlassian Stash and GitHub
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 · 668.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 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

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 Atlassian Stash
Pros of GitHub
    Be the first to leave a pro
    • 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
    • 42
    • 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
    • 8
      It integrates directly with Hipchat
    • 8
    • 8
      Beautiful user experience
    • 7
      Easy to discover new code libraries
    • 6
      Smooth integration
    • 6
      Cloud SCM
    • 6
      Nice API
    • 6
    • 6
    • 6
      It's awesome
    • 5
      Quick Onboarding
    • 5
    • 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
    • 3
    • 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
    • 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
    • 1

    Sign up to add or upvote prosMake informed product decisions

    Cons of Atlassian Stash
    Cons of GitHub
      Be the first to leave a con
      • 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

      Sign up to add or upvote consMake informed product decisions

      What companies use Atlassian Stash?
      What companies use GitHub?
      See which teams inside your own company are using Atlassian Stash 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 Atlassian Stash?
      What tools integrate with GitHub?

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

      What are some alternatives to Atlassian Stash and GitHub?
      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.
      GitHub Enterprise
      GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services.
      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.
      Use the full capability of Git and Mercurial in the SourceTree desktop app. Manage all your repositories, hosted or local, through SourceTree's simple interface.
      JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
      See all alternatives