Need advice about which tool to choose?Ask the StackShare community!
GitHub vs TortoiseSVN: What are the differences?
Introduction
GitHub and TortoiseSVN are both version control systems that are commonly used in software development projects. While they serve the same purpose of managing and tracking changes to source code, there are several key differences between the two.
Integration with Git vs Subversion: GitHub is primarily designed for hosting Git repositories, which is a distributed version control system. On the other hand, TortoiseSVN is a client for Subversion, which is a centralized version control system. This means that GitHub is tailored for distributed workflows, allowing multiple developers to work on different branches and merge changes easily, while TortoiseSVN follows a centralized model with a single repository and controlled access.
Graphical Interface vs Shell Integration: GitHub provides a web-based graphical interface that allows users to navigate repositories, track issues, manage pull requests, and view commit history. In contrast, TortoiseSVN integrates with the Windows Explorer shell, providing a seamless UI experience with context menus, overlays, and tooltips directly within the file system.
Collaboration and Social Features: GitHub offers a rich set of collaboration and social features, such as project boards, wikis, discussions, and the ability to follow other users and projects. These features facilitate community engagement, code reviews, and project management. TortoiseSVN, being primarily a version control client, lacks these social aspects and focuses more on efficient code management.
Branching and Merging: GitHub makes it incredibly easy to create branches, which are lightweight and enable developers to work on isolated features without affecting the main codebase. Merging these branches back into the main branch is also simplified with features like pull requests and automatic conflict resolution. TortoiseSVN, while supporting branching and merging, requires more manual intervention and can sometimes result in conflicts that need to be resolved by the user.
Open Source vs Proprietary Software: GitHub is an open-source platform, allowing anyone to create repositories, collaborate on projects, and contribute to the community. This fosters a culture of openness, transparency, and shared knowledge. TortoiseSVN, while free to use, is a proprietary software developed by a single company, with a more controlled and regulated environment.
Workflows and Ecosystem: GitHub has gained immense popularity in the software development industry, and as a result, many tools, libraries, and frameworks are built with GitHub integration in mind. Its extensive ecosystem includes features like continuous integration and deployment (CI/CD) services, code review tools, project management integrations, and numerous third-party applications. TortoiseSVN, being more specialized in Subversion, has a more limited ecosystem with fewer integrations and plugins available.
In Summary, GitHub, with its distributed nature, graphical interface, rich collaboration features, streamlined branching and merging, open-source philosophy, and extensive ecosystem, offers a powerful and flexible version control platform that caters to the needs of modern software development projects. On the other hand, TortoiseSVN, with its centralized model, seamless Windows integration, focus on efficient code management, proprietary nature, and relatively simpler workflow, provides a more straightforward solution for version control in certain scenarios.
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 GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup867
- Issue tracker504
- Great community487
- Remote team collaboration483
- Great way to share449
- Pull request and features planning442
- Just works147
- Integrated in many tools132
- Free Public Repos122
- Github Gists116
- Github pages113
- Easy to find repos83
- Open source62
- Easy to find projects60
- It's free60
- 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
- Standard in Open Source collab10
- Newsfeed10
- Fast8
- Beautiful user experience8
- It integrates directly with Hipchat8
- Easy to discover new code libraries7
- Smooth integration6
- Integrations6
- Graphs6
- Nice API6
- It's awesome6
- Cloud SCM6
- Quick Onboarding5
- Remarkable uptime5
- CI Integration5
- Reliable5
- Hands down best online Git service available5
- Version Control4
- Unlimited Public Repos at no cost4
- Simple but powerful4
- Loved by developers4
- Free HTML hosting4
- Uses GIT4
- Security options4
- Easy to use and collaborate with others4
- Easy deployment via SSH3
- Ci3
- IAM3
- Nice to use3
- Easy and efficient maintainance of the projects2
- Beautiful2
- Self Hosted2
- Issues tracker2
- Easy source control and everything is backed up2
- Never dethroned2
- All in one development service2
- Good tools support2
- Free HTML hostings2
- IAM integration2
- Very Easy to Use2
- Easy to use2
- Leads the copycats2
- Free private repos2
- Profound1
- Dasf1
Pros of TortoiseSVN
- Easy to use1
Sign up to add or upvote prosMake informed product decisions
Cons of GitHub
- Owned by micrcosoft55
- Expensive for lone developers that want private repos38
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos9
- Limited featureset for issue management4
- Does not have a graph for showing history like git lens3
- GitHub Packages does not support SNAPSHOT versions2
- No multilingual interface1
- Takes a long time to commit1
- Expensive1